Re: Ask help:why my 64-bit ELF file could not run at the 64-bit mips cpu

[Dominic <dominicwj@gmail.com>]

Hi Jan,

Thanks a lot for your precious reply! I try to use -static to compile
the program, then the 64-bit program can run, so it should be the
library related other than 64-bit instruction or addressing related.
Then I stored the 64-bit libraries in nfs, and mount it on the target
board, after adding the path to ld.so.conf and 'ldconfig', the program
compiled without -static still does not run. Shall I miss something?

Thanks!
BR/Dominic


On Fri, Apr 23, 2010 at 1:11 AM, Jan Rovins <janr@adax.com> wrote:
> Jian Wang wrote:
>>
>> Hi,
>>
>>  I have a 64-bit mips cpu, and compiled a 64-bit application, but this
>>  application could not run. (the target is running Linux)
>>  The details is:
>>  1)if I compile the application with -mabi=n64, this program could not
>>  run, when I run it in the shell, it prompts "command not found"
>>  2)but if I compile the application with -mabi=n32, it runs well and
>>  gives the correct result.
>>
>>  I am wondering why with "-mabi=n64", this program could not run? I
>>  checked the CP0(status register), Bit px=0b0, KX=0b1, SX=0b1, UX=0b1,
>>  it seems that in User Mode, it accepts 64-bit operation.
>>
>>  Anybody could give me some help? Any comments is much appreciated!!
>>
>>  BR/Dominic
>>
>>
>
> Perhaps you do not have the "n64" system libraries set up correctly in
> userspace.
> I have seen the "command not found" error when some fundamental libraries or
> the loader was missing.
>
> Do you have a /lib64 & /user/lib64?
> Run the file command on some of those libraries & see if they are n64 or n32
> libs.
>
> double check your ld.so.conf to make sure it points to every thing you need.
> re run ldconfig if you change something.
>
>
> Jan
>
>