topic Re: Re: Timesys Linux BusyBox - Why I can't start a application from a shell in common way? in Vybrid Processors

Timesys Linux BusyBox - Why I can't start a application from a shell in common way?

dragan — Fri, 17 Oct 2014 22:11:49 GMT

Respected Colleagues,

after who knows which factory build I cannot start application from a shell with command "./Test".

BusyBox v1.20.2 (2014-10-17 23:46:34 CEST) built-in shell (ash)

Enter 'help' for a list of built-in commands.

# ls

TEST dev lib media proc sbin usr

bin etc linuxrc mnt root sys var

config home lost+found opt run tmp

# cd TEST

# ls

Test

# ./Test

-/bin/sh: ./Test: not found

Can somebody tell why is that, and how to solve this?

Thanks in advance.

With best regards,

Dragan Kujovic

Re: Timesys Linux BusyBox - Why I can't start a application from a shell in common way?

kef2 — Sat, 18 Oct 2014 18:14:50 GMT

Hi Dragan,

did you build Test with DS-5 GCC or with Timesys GCC? DS-5 GCC compiled applications need availability of

/lib/ld-linux-armhf.so.3

As a workaround you may make a soft link pointing to /lib/ld-linux.so.3

Re: Timesys Linux BusyBox - Why I can't start a application from a shell in common way?

dragan — Sat, 18 Oct 2014 18:37:31 GMT

Respected Edward,

build was made with DS-5 GCC. But interesting is that I got this problem few days ago, when I compiled proram with arm7-a CPU option and with hard float option, instead of arm4t CPU option and soft float option that I used before.

What do you think about that?

Also, can you explain how and where to make soft link pointing to /lib/ld-linux.so.3.

Thanks in advance.

With best regards,

Dragan Kujovic

Re: Re: Timesys Linux BusyBox - Why I can't start a application from a shell in common way?

kef2 — Sun, 19 Oct 2014 06:04:32 GMT

Try to un-tar attachment to your Vybrid RFS /lib folder.

Re: Re: Timesys Linux BusyBox - Why I can't start a application from a shell in common way?

dragan — Sun, 19 Oct 2014 07:38:36 GMT

Respected Edward,

thanks for your effort.

Yes, with your patch executable file compiled with ARM DS-5 GCC Compiler can work under default Timesys Linux distribution.

If I use ARM DS-5 CORRECT compiler and linker CPU option for Vybrid A5 core "-march=armv7-a" executable work under default Timesys Linux distribution only with your patch.

If I use ARM DS-5 INCORRECT compiler and linker CPU option for Vybrid A5 core "-march=armv4t" executable work under default Timesys Linux distribution.

I think that Timesys must include your patch in the Timesys Linux distribution (Vybrid RFS /lib folder), to allow correct Vybrid A5 CPU Type choice in GCC Compiler / Linker.

With best regards,

Dragan Kujovic