linking against an alternate ld.so

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I have been trying and trying to get glibc/binutils/gcc built into a locally rooted tree. For example /foo/bar/glibc/2.5/lib/ld-2.5.so as opposed to /lib/ld-2.5.so.  I have gotten glibc to behave, but subsequently built software, including binutils still links against the system-wide ld.so. I have tried -Wl,-nostdlibs as a CFLAG, and -nostdlibs as an LDFLAGS, with the appropriate -Ls, but that ends up "breaking" gcc.  If I compile without CFLAGS/LDFLAGS set the compilations succeed, but each time ldd (/foo/bar/glibc/2.5/bin/ldd) resolves back to the system-wide library. Objdump also reports the system wide so.

Contents of section .interp:
 400200 2f6c6962 36342f6c 642d6c69 6e75782d  400210 7838362d 36342e73 6f2e3200           /lib64/ld-linux-x86-64.so.2.

Would someone point me in the right direction on this. I would greatly appreciate a nudge in the right direction.


/tired of banging my head against this.



[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux