> libraries and stubs on the link line, including -llibc, -lm and the
> obligatory /usr/lib/crt1.o or /usr/lib/gcrt1.o - stracing a regular
> compiler will show you which libraries and stubs it links applications
> with, by default.
or use gcc -v ;)
=
guy keren <[EMAIL PROTECTED]> writes:
> actually, this is easier then it sounds. all you need to do is make sure
> processes linked with different libraries, look for them in different
> directories. this can be done either during compile (actually link) time,
> with the '-rpath' switch of gnu ld
On 25 Mar 2002, Oleg Goldshmidt wrote:
> I solved my immediate problem by installpkging the development tools
> from slackware-8.0 over the original system (got OK from the vendor).
> However, I am still curious about peace and co-existence of various
> glibc's, so if anyone has any clue, do let
I solved my immediate problem by installpkging the development tools
from slackware-8.0 over the original system (got OK from the vendor).
However, I am still curious about peace and co-existence of various
glibc's, so if anyone has any clue, do let me know.
Thanks for people who emailed and cal
Hi,
First, executive summary:
I would like to do one of the following:
* find binaries of various development tools (binutils, gcc, gdb),
that will work with a particular version of glibc (2.2.2).
* make two different versions of glibc (2.2.2 and 2.2.3) co-exist
on one system.
Now, here
