Re: [Boost-build] gcc.jam broken on 64-bit FreeBSD

Subject: Re: [Boost-build] gcc.jam broken on 64-bit FreeBSD
From: Steve M. Robbins (steve_at_[hidden])
Date: 2009-07-19 22:55:12

On Sun, Jul 19, 2009 at 10:39:23PM +0400, Vladimir Prus wrote:
> On Sunday 19 July 2009 Bruce Simpson wrote:
> 
> > Hi all,
> > 
> > This is just to say that Boost on FreeBSD is chock-a-block with 
> > regression failures on the amd64 platform.
> > I traced the issue back to this thread:
> >     http://lists.boost.org/boost-build/2008/10/20471.php
> > 
> > It appears that I have to get rid of the lib32 stuff, to get the linker 
> > to do the right thing, otherwise I get lots of these messages:
> > 
> > /libexec/ld-elf.so.1: /usr/lib32/libm.so.5: unsupported file layout
> > 
> > This is an obvious build/run problem with the LD_RUN_PATH; FreeBSD 
> > 64-bit binaries cannot dynamically link with 32-bit binaries, 
> > unless they use some form of explicit thunk. FreeBSD's rtld will 
> > not thunk on its own.
> 
> Do you happen to know why Linux does not have any problems on 64-bit
> platforms? Is there some fundamental difference in behaviour, or
> something else?

I'm reasonably certain that Linux will have the same problem, *if* the
32-bit libs are installed.  I don't have them installed, for example,
so the "Debian-Sid" regression testing works [1].

As I explained before [2], setting LD_LIBRARY_PATH will certainly
cause more problems than it solves.  Anyone who is testing Boost with
multiple compilers can easily set LD_LIBRARY_PATH themself [3].

My recommendation remains to simply remove this piece of gcc.jam.

Regards,
-Steve

[1] http://www.boost.org/development/tests/release/developer/summary.html
[2] http://lists.boost.org/boost-build/2008/10/20501.php
[3] http://lists.boost.org/boost-build/2008/10/20511.php