did you try compiling gcc itself with -Wl,--dynamic-linker ? the new gcc
then should then default link to ur custom glibc. also, if you can find
some solution to shared library problem that i mentioned, it would be
very helpful.
aseem.
KRAJCSOVITS Gyorgy wrote:
Hi, thanks for the reply,
yes -Wl,--dynamic-linker works, but when I'm compiling big programs
it is sometimes impossible (ok, very hard) to change the linker for
every link step. It would be better to have gcc (or ld) automatically
do this.
And I need gcc to search other directories for system header files
as well.
bye, krajo
On Thu, 15 Sep 2005, Aseem Rastogi wrote:
i am not sure about existing application but for a new program
-Wl,--dynamic-linker option works. i successfully did it for simple
hello world kind of programs but when i created shared libraries
using this option, it didn;t work and they seemed to be linked to
default linker.
try compiling gcc with this option to escape --dynamic-linker everytime.
regards,
aseem.
KRAJCSOVITS Gyorgy wrote:
Hi,
I'd like to compile a gcc that uses:
- /opt23/usr/include instead of /usr/include
(and similar for other system include dirs)
- instructs linker to use /opt23/lib/ld-linux.so.2 instead of
/lib/ld-linux.so.2
(Maybe this is a binutils issue, but it seems like binutils gets its
deafults from gcc when compiling binutils)
The idea is to be able to compile programs for another glibc, but
I'm not root, so I won't be able to use it in it's normal location.
So /lib/ld-linux.so.2 won't point to the new one. I tried to create
a cross compile toolchain but was unsuccessfull so far.
Is there a way to change the dynamic linker of an existing
application ?
From /lib/ld-linux.so.2 to /opt23/lib/ld-linux.so.2 ?
bye, krajo
--
The end is always good. If it's not good, it's not the end.
--
The end is always good. If it's not good, it's not the end.
