mm_mod_auth_ldap for two different apache versions, 2.0.49 or 2.2.4. On 2.0.49 using mm_mod_auth_ldap 3.07,./configure --prefix=/opt/hpws/apache/mm_mod_auth_ldap307/ --with-apache-dir=/opt/hpws/apache --with-apache-ver=2 --with-ldap-dir=/opt/openldap --with-mem-cache --with-apxs=/opt/hpws/apache/bin
I encounter the following during the make: ================================== ***Creating module** mod_auth_ldap v3.07 for Apache 2.x *******/opt/hpws/apache/bin/apxs -c mm_mod_auth_ldap.o -L/opt/openldap//lib ./libs/libghthash/src/.libs/libghthash.a -lldap -llber -lnsl /opt/hpws/apache/build/libtool --mode=link ld -b -o mm_mod_auth_ldap.la -module -avoid-version -module -avoid-version mm_mod_auth_ldap.o -L/opt/openldap//lib ./libs/libghthash/src/.libs/libghthash.a -lldap -llber -lnsl
*** Warning: Linking the shared library mm_mod_auth_ldap.la against the *** static library ./libs/libghthash/src/.libs/libghthash.a is not portable!*** Warning: Linking the shared library mm_mod_auth_ldap.la against the non-libtool
*** objects mm_mod_auth_ldap.o is not portable!rm -fr .libs/mm_mod_auth_ldap.la .libs/mm_mod_auth_ldap.* .libs/mm_mod_auth_ldap.*
ar cru .libs/mm_mod_auth_ldap.al ./libs/libghthash/src/.libs/libghthash.a ranlib .libs/mm_mod_auth_ldap.al creating mm_mod_auth_ldap.la(cd .libs && rm -f mm_mod_auth_ldap.la && ln -s ../mm_mod_auth_ldap.la mm_mod_auth_ldap.la)
====================================This looks good except there isn't any ld command (I removed the --silent from the apxs libtool call to see all cmds). The shared lib file is never created because the ld command is never attempted, hence the make install fails.
If I try the same with attempt with apache 2.2.4 and mm_mod_auth_ldap 3.11./configure --prefix=/tmp/apache/mm_mod_auth_ldap311/ --with-apache-dir=/tmp/apache --with-apache-ver=2.2 --with-ldap-dir=/opt/openldap --with-mem-cache --with-apxs=/tmp/apache/bin
I get the following... ========================= ***Creating module** mod_auth_ldap v3.11 for Apache 2.2.x *******/tmp/apache/bin/apxs -c mm_mod_auth_ldap.o -L/opt/openldap//lib -L./libs/libghthash/src/.libs -lghthash -lldap -llber -lnsl /tmp/apache/build/libtool --silent --mode=link gcc -o mm_mod_auth_ldap.la -rpath /tmp/apache/modules -module -avoid-version mm_mod_auth_ldap.o -L/opt/openldap//lib -L./libs/libghthash/src/.libs -lghthash -lldap -llber -lnsl
*** Warning: This system can not link to static lib archive /home/a26811/ldap/mm_mod_auth_ldap3.11/libs/libghthash/src/.libs/libghthash.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.libtool: link: cannot build libtool library `mm_mod_auth_ldap.la' from non-libtool objects on this host: mm_mod_auth_ldap.o
apxs:Error: Command failed with rc=65536 . *** Error exit code 1 Stop. ==========================I've tried other combo's of 3.11 on 2.0.49 and both combos not using gcc but rather the hp cc compiler. The errors are similar at the same link point, but all slightly different. I've even tried to cobble together a manual ld command but haven't found the right combo (unresolved symbols like ap_requires and main).
I'm desperate for some solution. Using 2.0.49 (the currently installed web server) would be preferable, but the upgrade to 2.2.4 could probably be swung. I'm guessing the same thing is wrong for all build attempts.
And using 3.11 on 2.2.4 on a Solaris 8 machine works like a charm using the same basic build process.
Thanks for any help. Brian --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|