Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 28 Oct 2008 10:18:10 +1030
From:      "Daniel O'Connor" <doconnor@gsoft.com.au>
To:        "M. Warner Losh" <imp@bsdimp.com>
Cc:        pisymbol@gmail.com, freebsd-hackers@freebsd.org, olli@lurza.secnetix.de, freebsd-questions@freebsd.org, wojtek@wojtek.tensor.gdynia.pl
Subject:   Re: Why does adding /usr/lib32 to LD_LIBRARY_PATH break 64-bit ?binaries?
Message-ID:  <200810281018.18786.doconnor@gsoft.com.au>
In-Reply-To: <20081027.090116.-1827344390.imp@bsdimp.com>
References:  <freebsd-hackers.79409.1224892331.200810250958.15130.doconnor@gsoft.com.au> <200810271411.m9REB6te015188@lurza.secnetix.de> <20081027.090116.-1827344390.imp@bsdimp.com>

next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart6193595.7Yc4fJACZC
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Tuesday 28 October 2008 01:31:16 M. Warner Losh wrote:
> 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 librari=
es
> :  > :)
> :
> : 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...

Good point..
The problem is really the Linux linker - it will find a FreeBSD library and=
=20
try and use it ahead of a Linux one later in the search path - this prevent=
s=20
stuff working :)

I have this exact problem with libfontconfig and Xilinx ISE.

Perhaps instead of ignore, use last.. But then it doesn't really matter for=
=20
the FreeBSD linker - I imagine I would have to convince Linux folks it's a=
=20
good idea.

=2D-=20
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C

--nextPart6193595.7Yc4fJACZC
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBJBlNC5ZPcIHs/zowRAq5HAJ4tagADbGaxFu1WvSKYl9pZcsFs4gCgmwNv
tDsw/tZ5vB0itN7IneoRVLw=
=YXsF
-----END PGP SIGNATURE-----

--nextPart6193595.7Yc4fJACZC--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200810281018.18786.doconnor>