Received: (qmail 18239 invoked by uid 501); 20 Nov 2001 15:54:08 -0000 Message-Id: <20011120155408.18238.qmail@apache.org> Date: 20 Nov 2001 15:54:08 -0000 From: Bela Gazdy Reply-To: bela@emory.edu To: submit@bugz.apache.org Subject: Will not create *.so objects when DSO modules requested X-Send-Pr-Version: 3.110 >Number: 8812 >Category: os-aix >Synopsis: Will not create *.so objects when DSO modules requested >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: closed >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Tue Nov 20 08:00:00 PST 2001 >Closed-Date: Sat Dec 01 20:42:53 PST 2001 >Last-Modified: Sat Dec 01 20:42:53 PST 2001 >Originator: bela@emory.edu >Release: httpd-2_0_28 >Organization: >Environment: AIX 4.3.3.0-ML09; IBM's xlC-3.1.4 AND AIX 5.1.0.0-ML01; IBM's VAC-5.0.2 >Description: On AIX 4.3.3 / cc (xlC): CC=cc ./configure --enable-mods-shared=most ------------------------------------------- ... checking whether to enable mod_so... yes updating cache ./config.cache loading cache ./config.cache within ltconfig checking host system type... powerpc-ibm-aix4.3.3.0 checking for ranlib... ranlib checking whether we are using GNU C... no checking for object suffix... o checking for executable suffix... (cached) no checking for cc option to produce PIC... none checking if cc supports -c -o file.o... no checking if we can lock with hard links... yes checking if cc static flag -bnso -bI:/lib/syscalls.exp works... none checking whether ln -s works... yes checking for non-GNU ld... /bin/ld checking if the linker (/bin/ld) is GNU ld... no checking whether the linker (/bin/ld) supports shared libraries... yes checking for BSD-compatible nm... /bin/nm -B checking command to parse /bin/nm -B output... ok checking how to hardcode library paths into programs... immediate checking for /bin/ld option to reload object files... -r checking dynamic linker characteristics... aix4.3.3.0 ld.so checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... no checking for objdir... .libs creating shlibtool ... --------------------------------------------------------------------------- This looks good, but then make, 'make install' puts the following in /usr/local/apache2/modules: libmod_access.a -> libmod_access.so.0.0.0 libmod_access.so.0 -> libmod_access.so.0.0.0 mod_access.la .... and similarly for other modules. httpd.conf wants mod_MODULE.so files. ====================================================================== AIX 5.1.0.0 is worst; CC=cc ./configure --host=rs6000-ibm-aix5.1.0.0 --enable-mods-shared=most gives ---------------------------------------------------------------------- ... checking whether to enable mod_so... yes updating cache ./config.cache loading cache ./config.cache within ltconfig checking host system type... rs6000-ibm-aix checking for ranlib... ranlib checking whether we are using GNU C... no checking for object suffix... o checking for executable suffix... (cached) no checking for cc option to produce PIC... none checking if cc supports -c -o file.o... no checking if we can lock with hard links... yes checking if cc static flag works... checking whether ln -s works... yes checking for non-GNU ld... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... no checking whether the linker (/usr/bin/ld) supports shared libraries... no checking for BSD-compatible nm... /usr/bin/nm -B checking command to parse /usr/bin/nm -B output... ok checking how to hardcode library paths into programs... unsupported checking for /usr/bin/ld option to reload object files... -r checking dynamic linker characteristics... no checking if libtool supports shared libraries... no checking whether to build shared libraries... no checking whether to build static libraries... yes ----------------------------------------------------------------------------- which does not even look good. make, 'make install' puts the following files in /usr/local/apache2/modules: mod_access.la ... and similarly for other modules; On both platforms, ./httpd -l gives: core.c prefork.c http_core.c mod_so.c ========================================================================= P.S.: On both platforms, apache-1.3.22 configures, compiles, and installs as expected. (the right mod_MODULE.so files in 'libexec') The same 'libtool' is installed on both machines: libtool --version /usr/opt/freeware/bin/libtool[315]: /usr/linux/bin/echo: not found. ltmain.sh (GNU libtool) 1.3.5a (1.385.2.236 2000/10/30 23:25:09) Installed libtool-1.4.2, with same results...:( ========================================================================= Thank you for this forum! -Bela >How-To-Repeat: >Fix: Suspicious AIX - libtool interaction????? >Release-Note: >Audit-Trail: Comment-Added-By: trawick Comment-Added-When: Wed Nov 28 14:00:31 PST 2001 Comment-Added: FYI... folks are actively working on getting DSO builds of Apache working on AIX. State-Changed-From-To: open-closed State-Changed-By: trawick State-Changed-When: Sat Dec 1 20:42:53 PST 2001 State-Changed-Why: Fixes were committed today to get Apache 2.0 DSOs working on AIX. It will be in the next alpha/beta of Apache 2.0, or you can get it via CVS. Note that currently a funky LoadModule statement is needed: LoadModule include_module libmod_include.a\ (libmod_include.so.0) Hopefully this can be resolved. Look at http://www.apache.org/~trawick/aixstatus.html for some more comments on outstanding issues for Apache 2.0 on AIX and let me know if you have any questions or concerns. As always, thanks for using Apache. >Unformatted: [In order for any reply to be added to the PR database, you need] [to include in the Cc line and make sure the] [subject line starts with the report component and number, with ] [or without any 'Re:' prefixes (such as "general/1098:" or ] ["Re: general/1098:"). If the subject doesn't match this ] [pattern, your message will be misfiled and ignored. The ] ["apbugs" address is not added to the Cc line of messages from ] [the database automatically because of the potential for mail ] [loops. If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request from a ] [developer. Reply only with text; DO NOT SEND ATTACHMENTS! ]