Date: Fri, 08 Feb 2002 10:35:42 -0800 From: Terry Lambert <tlambert2@mindspring.com> To: Maxim Sobolev <sobomax@FreeBSD.org> Cc: Ruslan Ermilov <ru@FreeBSD.org>, Jason Evans <jasone@canonware.com>, jdp@FreeBSD.org, deischen@FreeBSD.org, jasone@FreeBSD.org, hackers@FreeBSD.org, jlemon@FreeBSD.org Subject: Re: Linking libc before libc_r into application causes weird problems Message-ID: <3C641A7E.B1A5B6F8@mindspring.com> References: <1013147180.73417.2.camel@notebook> <20020207234233.D23162@canonware.com> <3C639A8C.6D100326@FreeBSD.org> <3C63A62D.3E4A4FC4@mindspring.com> <3C63AD02.79BA5AF5@FreeBSD.org> <20020208164132.D78163@sunbay.com> <3C63E5D1.1E423698@FreeBSD.org> <20020208172237.G78163@sunbay.com> <3C640DDE.78417F5C@mindspring.com> <3C6412EA.2605CDB@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Maxim Sobolev wrote: > > Yes, this is exactly the case: the shared library is linked > > against libc.so. THis is actually legal, and, in some cases, > > desirable. > > > > In the "Evolution" case, though, it's bogus. > > As you can see from my log there was no library explicitly linked with > libc and no -lc command line option, but resulting executable ended up > with libc recorded right before libc_r. Any clues? Answer my other questions. In the course of obtaining the answers, you will be presented with all the necessary clues to resolve your mystery. 8-). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3C641A7E.B1A5B6F8>