>Number: 4853 >Category: config >Synopsis: explicit knowlege about shared object support for freebsd4.0 >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Thu Aug 12 04:40:00 PDT 1999 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.3.6 >Environment: [EMAIL PROTECTED]:~$ uname -a FreeBSD threads.polyesthetic.org 4.0-CURRENT FreeBSD 4.0-CURRENT #11: Wed Aug 11 08:57:53 MST 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/THREADS i386 >Description: During configure, I got this message:
** WARNING: We have no explicit knowledge about shared object ** support for your particular platform. But perhaps you have ** luck: We were able to guess the compiler and linker flags ** for creating shared objects from your Perl installation. ** If they actually work, please send the following information ** for inclusion into later releases to new-httpd@apache.org or make ** a suggestion report at http://www.apache.org/bug_report.html: ** PLATFORM=i386-whatever-freebsd4.0 ** CFLAGS_SHLIB=-DPIC -fpic ** LDFLAGS_SHLIB=-shared ** LDFLAGS_SHLIB_EXPORT= It does in fact work well. I had to add --enable-rule=SHARED_CORE, as well. Here is my config.status: CC="cc" \ CFLAGS="-O2 -pipe -Wall" \ ./configure \ "--with-layout=Apache" \ "--enable-shared=max" \ "--enable-module=all" \ "--enable-suexec" \ "--suexec-caller=http" \ "--with-perl=/usr/bin/perl" \ "--enable-rule=SHARED_CORE" \ "$@" >How-To-Repeat: >Fix: >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, you need] [to include <[EMAIL PROTECTED]> 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! ]
