From: Michael van der Westhuizen (michael_at_[hidden])
Date: 2005-03-22 13:45:05
On Mar 22, 2005, at 6:11 PM, Caleb Epstein wrote:
> On Tue, 22 Mar 2005 13:02:38 -0000, John Maddock
> <john_at_[hidden]> wrote:
>>> Who should I work with to get the appropriate tests marked as
>>> known-to-fail or N/A? This exercise is necessary for some
>>> gcc-on-Solaris tests as well. For instance, all of the "*_lib" tests
>>> in Boost.Thread fail because "gcc -static" won't link with *any*
>>> shared libs. Solaris does not provide static versions of -lrt or
>>> -lthread, so these tests fail to link. There really should really be
>>> a "-prefer-static" option to gcc.. Alternately, the Jamfiles could
>>> hacked to use -Wl,-Bstatic / -Wl,-Bdynamic guards around the
>>> of the Boost.Thread lib for these tests.
>> That would probably be my preferred option, is it just a case of
>> adding -Wl,-Bdynamic to the very end of the command line? Rene would
>> probably know the best way to fix this.
> In my testing, I have found that you can't use "gcc -static" on
> Solaris if you have *any* shared libs to link with. It overrides even
> later uses of -Wl,-Bdynamic (in fact using both -static and
> -Wl,-Bdynamic causes a linker error - see below).
This might also be even more confusing on Solaris 10 - see this blog
entry: http://tinyurl.com/5sqxc for details.
[snip rest of message]
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk