Well, I also had the idea that the solution had to be as simple as just having it seperately in different directories, but the only way i could get it to work properly was if I created a chroot environment. My first (trivial) idea was that I should ofcourse just use the environment variable "LD_LIBRARY_PATH" to change the library search location. But for some reason this doesnt seem to work with the libc library. Maybe the dynamic linker uses functionality in libc to actually read and use library path variable and for that reason the libc library is fixed in location so that the linker can load it before evaluating the variable. Feel free to educate me though on how to do this properly, my experience here is purely on a "need to know basis" :-) 2009/11/21 Ian Lance Taylor <iant@xxxxxxxxxx>: > Tobias Nielsen <tobibobi@xxxxxxxxx> writes: > >> It would be great if the *libc library was statically linked together >> with binary program, but that is not possible - or is it? > > Static linking works on most systems. The glibc maintainers have > decided to prohibit it, but even with glibc it mostly works--except > for doing DNS lookups. I don't know whether uClibc supports static > linking or not. > > >> Is there any way that i can take a binary and then post link it >> statically with its dependent libraries. > > Not in the way you mean. But you can install both glibc and uClibc on > the same system, just install them in different directories. > > Ian > -- Tobias Nielsen ___________________________________ M.Sc Robotics Engineering. / Cand. Polyt Member of IEEE, ComSoc
