httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sander Temme <>
Subject Re: where to describe critical OS-specific requirements
Date Tue, 09 Apr 2002 04:45:58 GMT
> Any Mac OS X folks watching now?  Don't we need something like this in
> /dist/httpd/patches/apply_to_2.0.35/README.html?

>   * OS X
>        1. up-to-date libtool needed
>           Install libtool 1.4.2 separately. Once the Apache source
>           distribution has been  unpacked, run ./buildconf before ./configure.

Hm... The MacOSX Developer Tools come with GNU libtool (called glibtool but
buildconf knows about this) 1.3.5, which is almost functional. It needs one
little patch:

--- /usr/share/libtool/ltconfig.bak     Tue Oct  2 17:53:33 2001
+++ /usr/share/libtool/ltconfig Thu Apr  4 09:20:07 2002
@@ -1372,7 +1372,7 @@
   darwin* | rhapsody*)
-    allow_undefined_flag='-undefined warning'
+    allow_undefined_flag='-undefined suppress -flat_namespace'
     archive_cmds='$CC $(if test .$module = .yes; then echo -bundle; else
echo -dynamiclib; fi) $allow_undefined_flag -o $lib $libobjs $deplibs
     #archive_expsym_cmds="$archive_cmds"' && strip -s $export_symbols $lib'
     hardcode_direct=yes work on MacOS X 10.1 (Darwin 5.1 and onwards). Do this and one can
build Apache 2.0 with shared library support using nothing but Apple's
developer tools. 

Libtool 1.4.2 is broken on MacOS X. It suffers from a quoting error in zsh
which is used as /bin/sh on MacOSX. This problem is addressed by Pier at

But this requires a user-installed patch upon a user-installed libtool. I'm
in favour of the first option.


Covalent Technologies                   
Engineering group                                Voice: (415) 536 5214
645 Howard St.                                     Fax: (415) 536 5210
San Francisco CA 94105

   PGP Fingerprint: 1E74 4E58 DFAC 2CF5 6A03  5531 AFB1 96AF B584 0AB1

This email message is for the sole use of the intended recipient(s) and may
contain confidential and privileged information. Any unauthorized review,
use, disclosure or distribution is prohibited.  If you are not the intended
recipient, please contact the sender by reply email and destroy all copies
of the original message

View raw message