Static Library Linking Issue

[Gavin Norman]

I'm trying to link a module library that can be used for dlopen against a static lib. This is the issue I get:

/usr/local/bin/libtool --mode=link c++ -O2 -pipe -g -Wall -Wno-write-strings -DOPENBSD -pedantic -Wno-long-long -pthread -L/usr/local/lib -lexecinfo -lssl -lcrypto -o ldapplugin.la -rpath /usr/local/lib/zarafa -module ldapplugin_la-LDAPUserPlugin.lo ldapplugin_la-ldappasswords.lo ../../common/libcommon_util.la -lldap -liconv

*** Warning: This system can not link to static lib archive ../../common/libcommon_util.la.
*** 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.
*** But as you try to build a module library, libtool will still create
*** a static module, that should work as long as the dlopening application
*** is linked with the -dlopen flag to resolve symbols at runtime.
ar cru .libs/ldapplugin.a ldapplugin_la-LDAPUserPlugin.o ldapplugin_la-ldappasswords.o
ranlib .libs/ldapplugin.a
creating ldapplugin.la

I libcommon_util.la is created as a static library. A few suggestions from OpenBSD porters have been to add -fPIC to flags. I've added this to the LDFLAGS, CPPFLAGS, CXXFLAGS & CFLAGS for libcommon_util.la with no success.

Gavin Norman
E: address@hidden