Re: [jamboost] GCC/STLPort static linking failures (Was: [Thread] GCC 2.95/STLPort/Linux static lib failures)

From: Rene Rivera (grafik.list_at_[hidden])
Date: 2004-09-28 07:29:41

Aleksey Gurtovoy wrote:
> Folks,
> 
> Could somebody familiar with the gcc-stlport toolset answer Martin's
> question below?
> 
> Martin Wille writes:
> 
>>Aleksey Gurtovoy wrote:
>>
>>>Is it the test environment that is at failt here (from
>>>http://tinyurl.com/5t5mf):
>>>/usr/bin/ld: cannot find -lstlport_gcc_stldebug_static
>>
>>There is no file named "libstlport_gcc_stldebug_static.a" here.
>>Instead, there is "libstlport_gcc_stldebug.a". Is the library
>>name being generated incorrectly, or would the additional
>>"static" in the library name indicate something different than
>>what the ".a" indicates in contrast to the ".so" extension used
>>by shared libraries?
>>
>>
>>
>>>collect2: ld returned 1 exit status
>>> set -e 
>>> LD_LIBRARY_PATH=/usr/local/gcc-2.95.3/stlport-4.5.3/lib:/usr/local/gcc-2.95.3/lib:$LD_LIBRARY_PATH 
>>
>>The path is being set correctly.
>>
>>Regards,
>>m
> 
> 
> Thanks in advance,

The problem stems from the change you made to stlport.jam:

----------------------------
Revision : 1.8
Date : 2004/9/19 10:54:3
Author : 'agurtovoy'
State : 'Exp'
Lines : +4 -2
Description :
fix STLPort linking issue
===================================================================
RCS file: /cvsroot/boost/boost/tools/build/v1/stlport.jam,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- stlport.jam	1 Sep 2004 05:37:03 -0000	1.7
+++ stlport.jam	19 Sep 2004 10:54:03 -0000	1.8
@@ -100,5 +100,7 @@
flags $(CURR_TOOLSET) DEFINES <runtime-build>debug : _STLP_DEBUG=1 
_STLP_DEBUG_UNINITIALIZED=1 ;
flags $(CURR_TOOLSET) DEFINES <runtime-link>dynamic : 
_STLP_USE_DYNAMIC_LIB=1 ;

-flags $(CURR_TOOLSET) FINDLIBS 
<stlport-iostream>on/<runtime-build>debug : 
$(STLPORT_LIB_BASE_NAME)_stldebug ;
-flags $(CURR_TOOLSET) FINDLIBS 
<stlport-iostream>on/<runtime-build>release : $(STLPORT_LIB_BASE_NAME) ;
+flags $(CURR_TOOLSET) FINDLIBS 
<stlport-iostream>on/<runtime-build>debug/<runtime-link>static : 
$(STLPORT_LIB_BASE_NAME)_stldebug_static ;
+flags $(CURR_TOOLSET) FINDLIBS 
<stlport-iostream>on/<runtime-build>debug/<runtime-link>dynamic : 
$(STLPORT_LIB_BASE_NAME)_stldebug ;
+flags $(CURR_TOOLSET) FINDLIBS 
<stlport-iostream>on/<runtime-build>release/<runtime-link>static : 
$(STLPORT_LIB_BASE_NAME)_static ;
+flags $(CURR_TOOLSET) FINDLIBS 
<stlport-iostream>on/<runtime-build>release/<runtime-link>dynamic : 
$(STLPORT_LIB_BASE_NAME) ;
----------------------------

I don't know which platforms have the *_static versions for which you 
made the change to fix the link problem. But I guess you would have to 
special case for those platforms. Or revert this change, and move it to 
the toolset specific *tools.jam file.

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