Re: [Boost-build] Boost 1.43.0 seems to produce broken libraries with MinGw version 4.5.0

Subject: Re: [Boost-build] Boost 1.43.0 seems to produce broken libraries with MinGw version 4.5.0
From: Robert Ramey (ramey_at_[hidden])
Date: 2010-07-16 12:15:48

Peter Rockett wrote:
>>  In addition, we have observed that attempting to link against the
>> (seemingly) broken libraries produces a series of extra warning
>> messages
>> which do not appear when linking against the 4.4.0-built libs. See
>> the
>> attached screen shot. These may help in diagnosing what is wrong.
>>
>> Peter
>>
>>
>>
>>
>> On 15/07/10 22:30, Peter Rockett wrote:
>>>  We have been trying to build Boost 1.43.0 using MinGW. (Actually we
>>> have been trying to build a package which relies on Boost.) We have
>>> encountered some weird problems with the ultimate package, which
>>> made us investigate the Boost libraries we were building.
>>> Minimally, we have used:
>>>
>>> bjam --toolset=gcc install
>>>
>>> although we have also explicitly specified link= static, and
>>> runtime-link=shared, etc.
>>>
>>> Basically:
>>>
>>> 1) The build process with MinGW 4.5.0 appears to complete without
>>> error but any programs which use the resulting Boost libs crash
>>> immediately with what looks like an issue with loading a shared lib.
>>> We have tried running the Boost execution monitor test example but
>>> this fails.
>>>
>>> 2) Repeating the process with MinGW 4.4.0 produces working programs
>>> and the execution monitor example works fine.
>>>
>>> Therefore, we conclude that the libraries built with MinGW 4.5.0 are
>>> broken. MinGW 4.4.0 seems to produce good libs.
>>>
>>> Could someone advise if they have had success with building with gcc
>>> 4.5.0 on, say, Linux. Or is this just a problem with MinGW 4.5.0?

I have no idea whether this is relevant, but it might be.

The serialization library fails to build on MinGW.  This has been traced
to the fact that the build for this compiler includes "visibility=hidden" 
which
is a new facility for gcc.  Turns out that the serialization library and
maybe others need to be tweaked to accomodate this new facility.
Until that happens, they won't work ith this switch.

Robert Ramey