Date: Fri, 08 Feb 2002 09:53: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: <3C6410A6.495CFD3A@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> <3C63E961.45706408@mindspring.com> <20020208172503.H78163@sunbay.com> <3C63F3FE.D4E73334@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Maxim Sobolev wrote: > But no library has it here! libc comes out of blue just before libc_r > - see attached script. Perhaps I'm missing something, but I can't > figure out where it comes from, could you? What does your patched ldd say about each and every one of those .so's you are linking in perhaps being linked against libc.so, or linked against something linked against something ... linked against something linked against libc.so? Are *any* of the object files created with "ld -r"? Which binutils are you using? Who cut your hair? ;^). -- 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?3C6410A6.495CFD3A>