Re: [Boost-users] [1.34] using STLport 5.1.0 fails during linking

From: Vincent Torri (vtorri_at_[hidden])
Date: 2007-04-05 18:14:23

Hey,

I've tried something which is not the correct solution : adding symbolic 
links. Boost 1.34 seems to compile fine with STLport 5.1.0 or 5.1.3. At 
least, I know that there is no problem for the compilation itself. What 
needs to be fixed is the configuration.

Btw, There is a TODO in stlport.jam, that says that the configuration 
needs to support different settings according to the chose toolset. Maybe 
for Boost 1.34.1.

About the compilation itself, I just have some warnings about non virtual 
destructors.

Vincent Torri

On Thu, 5 Apr 2007, Vincent Torri wrote:

>
>
> On Thu, 5 Apr 2007, Rene Rivera wrote:
>
>>> tar jxvf STLport-5.1.0.tar.bz2
>>> cd STLport-5.1.0/build/lib
>>> make -f gcc.mak depend
>>> make -f gcc.mak
>>> make -f gcc.mak all-static
>>> make -f gcc.mak install
>>> make -f gcc.mak install-static
>>> cd ../..
>>> cp lib/libstlport* $HOME/local/lib/
>>> cp -R stlport $HOME/local/include/
>> 
>> That's essentially what I did with STLport 5.1.0, except on Windows
>> (MinGW+MSYS & BAT)
>> 
>> But I get:
>> 
>> libstlport.5.1.a
>> libstlport.5.1.dll.a
>> libstlportg.5.1.a
>> libstlportg.5.1.dll.a
>> libstlportstlg.5.1.a
>> libstlportstlg.5.1.dll.a
>
> That the problem of having different maintainer for Unix and Windows, I guess 
> :)
>
>>> I compiled Boost with that command line:
>>> 
>>> ../../boost-jam-3.1.13-1-linuxx86/bjam --prefix=$HOME/local stdlib=stlport 
>>> --toolset=gcc
>> 
>> Hm, all I can think of is to try using "stdlib=stlport-5.1.0".
>
> no change. Same error messages
>
>>> If needed, I can provide more informations on my system.
>> 
>> Some of the commands run by the bjam build might be illuminating.
>
> You can see the output here : http://pastebin.ca/425041
>
> Vincent Torri
>