Why does adding /usr/lib32 to LD_LIBRARY_PATH break 64-bit binaries?

Peter Jeremy peterjeremy at optushome.com.au
Fri Oct 24 12:51:06 UTC 2008


On 2008-Oct-24 10:43:04 +0200, Wojciech Puchar <wojtek at wojtek.tensor.gdynia.pl> wrote:
>> 6.1-RELEASE-amd64 machine.  If I add /usr/lib32 to my LD_LIBRARY_PATH
>> it breaks all of my binaries on my 64-bit machine.
>
>what do you expect else?

Well, the rtld should be smart enough to recognize 32-bit .so's and
skip them when binding a 64-bit executable.  Whilst having /usr/lib32
in LD_LIBRARY_PATH doesn't make sense from a solely FreeBSD perspective,
I have done similar things when writing cross-platform scripts (to
avoid having to use platform-dependent code).

>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.

-- 
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed behaviour.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20081024/d72ea2cd/attachment.pgp


More information about the freebsd-hackers mailing list