[gcc/HP-UX] link errors due to the wrong shared library suffix
--------------------------------------------------------------

         Key: STDCXX-166
         URL: http://issues.apache.org/jira/browse/STDCXX-166
     Project: C++ Standard Library
        Type: Bug
  Components: Build  
    Versions: 4.1.3    
 Environment:  $ uname -mrs && gcc -v
HP-UX B.11.11 9000/800
Reading specs from /usr/local/lib/gcc/hppa2.0w-hp-hpux11.11/3.4.2/specs
Configured with: /scratch/njs/pkgbuild/3.3.1/hpux-11/gcc-3.4.2/configure 
--enable-languages=c,c++ --enable-threads=posix --disable-nls --with-gnu-as 
--without-gnu-ld --with-as=/usr/local/bin/as --with-ld=/usr/ccs/bin/ld 
--with-libiconv-prefix=/usr/local --prefix=/usr/local
Thread model: posix
gcc version 3.4.2
    Reporter: Martin Sebor
     Fix For: 4.1.4


All programs fail to link with the shared stdcxx library due to the wrong 
library suffix (.so, should be .sl on HP-UX):

$ make strstream
generating dependencies for $(TOPDIR)/examples/manual/strstream.cpp
gcc -c -I/house/sebor/stdcxx-4.1.3/include/ansi    -D_RWSTD_USE_CONFIG 
-I/house/sebor/build/stdcxx-4.1.3-gcc-3.4.2/include 
-I/house/sebor/stdcxx-4.1.3/include 
-I/house/sebor/stdcxx-4.1.3/examples/include  -pedantic -nostdinc++ -O2  -Wall 
-W -Wcast-qual -Winline -Wshadow -Wwrite-strings -Wno-long-long -Wcast-align  
/house/sebor/stdcxx-4.1.3/examples/manual/strstream.cpp
gcc strstream.o -o strstream  -L/house/sebor/build/stdcxx-4.1.3-gcc-3.4.2/lib 
-lstd8d  -lsupc++ -lm
/usr/ccs/bin/ld: Can't find library: "std8d"
collect2: ld returned 1 exit status
make: *** [strstream] Error 1

$ ls -l ../lib/libstd8d.so
lrwxr-xr-x   1 sebor      nis             63 Mar 18 14:56 ../lib/libstd8d.so -> 
/house/sebor/build/stdcxx-4.1.3-gcc-3.4.2/lib/libstd8d.so.4.1.3


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to