This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: .so problem




LLeweLLyn Reese wrote:
Gergely Tamás <gertom at rgai dot hu> writes:


Hello!

I'm trying to cross-compile for arm-linux. After linking, the
executables contain "/usr/lib/ld.so.1" in the ".interp" section. But
the only similar file I have in the $(PREFIX)/lib directory is
ld-linux.so.2

- Could anyone tell me where the value of the ".interp" section comes from?
- Does /usr/lib/ld.so.1 comes with the linux system or belongs to
binutils or gcc or glibc?

[snip]


/usr/lib/ld.so.1 is expected to be the linker-loader on the target
    system - *not* on the host system. Check the target system for
    /usr/lib/ld.so.1 .


Sorry for not enough details, I'm trying to explain: on the target machine I have no /usr/lib/ld.so.1 but have a /lib/ld-linux.so.2. On the host in the $(PREFIX)/lib, I also have an ld-linux.so.2.


If I copy 'target' ld-linux.so.2 to ld.so.1, it segfaults. If I copy 'host'
ld-linux.so.2 to ld.so.1, it says: "error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory". I think that ld-linux.so.2 has its own search path. If I use LD_LIBRARY_PATH to set this, it also segfaults with both the 'target' and 'host' libc.so.6.


gertom

--
**************************************************************************
* Gergely Tamás                                    e-mail:gertom at rgai dot hu *
* ICQ:104783919                                    http://gertom.rgai.hu *
**************************************************************************


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]