The following reply was made to PR general/3291; it has been noted by GNATS.

From: "Ralf S. Engelschall" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc:  Subject: Re: general/3291: Can not load modules that have been configured
Date: Mon, 26 Oct 1998 11:13:49 +0100

 In article <[EMAIL PROTECTED]> you wrote:
 
 >  That doesn't make sense to me.
 >  
 >  ---------- Forwarded message ----------
 >  Date: Sun, 25 Oct 1998 17:23:19 -0600 (CST)
 >  From: Lawrence Bowie <[EMAIL PROTECTED]>
 >  To: [EMAIL PROTECTED]
 >  Subject: Re: general/3291: Can not load modules that have been configured
 >  
 >  Actually, if you add ....--enable-rule=SHARED_CORE to 
 >  
 >  ./configure --prefix=/home/www --activate-module=src/modules/php3/libphp3.a 
 >  --enable-shared=php3 --enable-module=most --enable-module=log_agent 
 >  --enable-module=log_referer --enable-module=usertrack 
 >  --enable-module=mmap_static --with-perl=/usr/local/bin/perl 
 > --enable-shared=max 
 >  
 >  Which is the original configuration. It will work just fine.
 >  Thank you for your help,
 
 Oh, it _DOES_ make sense when we take into account that he is using Solaris (a
 SVR4 platform) and not GCC. I don't know, but perhaps his WorkShop compiler
 links httpd (or calls the linker) httpd differently then GCC does. Especially
 the symbol exporting flag is missing. But with --enable-rule=SHARED_CORE this
 is not needed, because with a libhttpd.so the functions are available to the
 DSOs. So, the question is: What flag do we have to provide to the WorkShop
 compiler to force him to export the symbols of httpd?  Currently under Solaris
 we have LDFLAGS_SHLIB_EXPORT="", but perhaps we need something here for the
 non-GCC situation.  At least we have some more PRs which seems to be exactly
 the same problem. They are under Solaris and I couldn't find the problem under
 my setup (Solaris+gcc).
                                        Ralf S. Engelschall
                                        [EMAIL PROTECTED]
                                        www.engelschall.com

Reply via email to