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 15:14:15

On Sun, Jul 19, 2009 at 07:07:39PM +0100, 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, [...]

What, precisely, do you mean by "get rid of the lib32 stuff"?  Does
completely removing the following from tools/build/v2/tools/gcc.jam
fix your problem?

    # If gcc is installed in non-standard location, we'd need to add
    # LD_LIBRARY_PATH when running programs created with it (for unit-test/run
    # rules).
    if $(command)
    {
        # On multilib 64-bit boxes, there are both 32-bit and 64-bit libraries
        # and all must be added to LD_LIBRARY_PATH. The linker will pick the
        # right onces. Note that we don't provide a clean way to build 32-bit
        # binary with 64-bit compiler, but user can always pass -m32 manually.
        local lib_path = $(root)/bin $(root)/lib $(root)/lib32 $(root)/lib64 ;
        if $(.debug-configuration)
        {
            ECHO notice: using gcc libraries :: $(condition) :: $(lib_path) ;
        }
        toolset.flags gcc.link RUN_PATH $(condition) : $(lib_path) ;
    }

If so, I agree that removing this would be a good thing.  Please make
a note on https://svn.boost.org/trac/boost/ticket/2438

Regards,
-Steve