dynamic mod_shib

Clausen, Jörn joern.clausen at uni-bielefeld.de
Wed Oct 23 05:03:31 EDT 2019


I am trying to compile shibboleth-sp-3.0.4. All libraries, for 
shibboleth-sp itself and all requirements (log4shib, xmltooling and 
opensaml) are built as dynamic libraries, only the Apache modules are 
created as static libraries. libtool returns

*** Warning: linker path does not have real file for library -lgcc.
*** I have the capability to make that library automatically link in when
*** you link to this library.  But I can only do this if you have a
*** shared version of the library, which you do not appear to have
*** because I did check the linker path looking for a file starting
*** with libgcc and none of the candidates passed a file format test
*** using a regex pattern. Last file checked: /usr/lib/libgcc.a

*** Warning: libtool could not satisfy all declared inter-library
*** dependencies of module mod_shib_24.  Therefore, libtool will create
*** a static module, that should work as long as the dlopening
*** application is linked with the -dlopen flag.

Which is technically correct, I have only -lgcc_s. I get a similar 
warning for e.g. libshibsp.so, but this library is built nonetheless.

After the configure step, I changed in libtool

postdeps="-lstdc++ -lm -lgcc_s -lgcc -lc -lgcc_s -lgcc"


postdeps="-lstdc++ -lm -lgcc_s -lc"

and now I have (correctly linked) dynamic Apache modules. I have tried 
passing a corrected postdeps_CXX to configure, but it keeps including 
-lgcc. How can I fix the build process so that I don't have to tweak 
libtool manually?

Jörn Clausen
Plattformen & Serverdienste
BITS - Bielefelder IT-Servicezentrum

More information about the users mailing list