[boost] [regression] Link failures for intel-win32-7.1-vc6-stlport-4.5.3

From: Rene Rivera (grafik.list_at_[hidden])
Date: 2004-07-09 00:56:51

Before John Maddock left on vacation, lucky him, he asked me to look 
into how to fix the problems with linking failing under some 
circumstances for this toolset in the regression tests. His supposition 
was that the auto-linking was not generating the correct name for 
linking, and that we needed to fix either the auto-linking or the build 
to be consistent about the naming.

In looking at what is failing, as compared to what is not failing, my 
conclusion differs. The problem is that the failing tests are using 
auto-linking at all. As according to John himself one should not use it 
in the regression tests: "Please note however that this Jamfile will 
only build with compilers that do actually support auto-linking, so it 
should not be added to the regular regression tests." 
(http://boost.org/more/separate_compilation.html#testing) -- And the 
tests in question, signals, accidentally use both auto-linking and 
direct linking.

There are two ways of fixing this problem:

a) I automatically and globally <define>BOOST_ALL_NO_LIB=1 for all 
targets within Boost, or,

b) We change individually each test that uses an auto-link enabled 
library to <define>BOOST_ALL_NO_LIB=1

I'm currently leaning towards (b), even if it is more work, as it has 
less chances of breaking other tests and/or the regular builds of 
examples and the libraries themselves.

Comments?

-- 
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software.com
-- rrivera/acm.org - grafik/redshift-software.com - 102708583/icq