Date: Mon, 27 Oct 2008 09:01:16 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: freebsd-hackers@freebsd.org, doconnor@gsoft.com.au, pisymbol@gmail.com, freebsd-questions@freebsd.org, wojtek@wojtek.tensor.gdynia.pl, olli@lurza.secnetix.de Subject: Re: Why does adding /usr/lib32 to LD_LIBRARY_PATH break 64-bit ?binaries? Message-ID: <20081027.090116.-1827344390.imp@bsdimp.com> In-Reply-To: <200810271411.m9REB6te015188@lurza.secnetix.de> References: <freebsd-hackers.79409.1224892331.200810250958.15130.doconnor@gsoft.com.au> <200810271411.m9REB6te015188@lurza.secnetix.de>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <200810271411.m9REB6te015188@lurza.secnetix.de>
Oliver Fromme <olli@lurza.secnetix.de> writes:
: Daniel O'Connor wrote:
: > On Friday 24 October 2008 23:20:59 Peter Jeremy wrote:
: > > > this will make system trying to bind 32-bit libs to 64-bit program. it
: > > > can't work
: > >
: > > rtld shouldn't attempt to bind 32-bit libs to 64-bit programs.
: >
: > The same problem happens with the Linux run time linker - it merrily tries to
: > link FreeBSD libraries to Linux binaries with predictable results..
:
: You *can* link Linux libraries with FreeBSD binaries (and
: vice versa), if the library does not perform any syscalls,
: e.g. it is a pure computation library or similar.
:
: > That said it would be really nice if it ignored incompatible libraries :)
:
: No. Please don't put such pseudo-cleverness into rtld.
: It wouldn't be an improvement, in fact it might break some
: working configurations.
Yes. I have a bunch of printer drivers that I've used that link in
linux shared libraries... They are in ports...
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081027.090116.-1827344390.imp>