Date: Sat, 25 Oct 2008 08:49:19 -0400 From: "Alexander Sack" <pisymbol@gmail.com> To: "Daniel O'Connor" <doconnor@gsoft.com.au> Cc: freebsd-hackers@freebsd.org, Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl>, freebsd-questions@freebsd.org, Peter Jeremy <peterjeremy@optushome.com.au> Subject: Re: Why does adding /usr/lib32 to LD_LIBRARY_PATH break 64-bit binaries? Message-ID: <3c0b01820810250549r6c1f5614i27709c09d73a2018@mail.gmail.com> In-Reply-To: <200810250958.15130.doconnor@gsoft.com.au> References: <3c0b01820810231731s1b4d4659j7d1df8bf4abb229c@mail.gmail.com> <20081024104232.X21603@wojtek.tensor.gdynia.pl> <20081024125059.GE1137@server.vk2pj.dyndns.org> <200810250958.15130.doconnor@gsoft.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Oct 24, 2008 at 7:28 PM, Daniel O'Connor <doconnor@gsoft.com.au> 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.. > > One trick I use for that is to put a symlink in /compat/linux in the place the > problematic FreeBSD library is.. > > That said it would be really nice if it ignored incompatible libraries :) Yea. Also you go tot realize that if it didn't pick up /usr/lib32 shared objects then /lib would be searched as a last resort I believe since its the default path. As a result, things again would have just worked. Is this a bug or not in FreeBSD's rtld? -aps
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3c0b01820810250549r6c1f5614i27709c09d73a2018>