>My remaining problem was that, after compiling and linking a hellow prog, it
>expected ld-linux.so.2 to be in /lib rather than /usr/arm-new/lib where it's
>been installed. Is this correct behaviour? It's easily fixed, anyway
>(either by linking the file across or using
>``-Wl,-dynamic-linker=/usr/arm-new/lib/ld-linux.so.2'').
If you put ld-linux.so.2 anywhere other than /lib you need to update your GCC
specs appropriately.
>Also, running ldd on my newly-made hellow ELF executable (or the executables
>that glibc builds) dies with a register dump. Not an immediate problem.
>
>Incidentally, Debian appears to use a separate ld.so from the one in glibc.
>Why's that?
You might be thinking of the ld.so.1 which is used for libc4 binaries, or the
ld-linux.so.1 which is used for libc5 binaries on other platforms. Neither of
these will work with code compiled against glibc, nor will the corresponding
ldd.
Check your PATH and make sure you are running the version of ldd that was
newly built. If you still have trouble, let me know and I'll look into it.
p.
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
