You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Cliff Woolley <jw...@virginia.edu> on 2002/04/09 08:16:48 UTC
Re: where to describe critical OS-specific requirements (fwd)
Can we *please* apply this patch to the libtool on icarus?? That would
make the lives of we httpd'ers sooooo much easier...
Thanks,
Cliff
---------- Forwarded message ----------
Date: Mon, 08 Apr 2002 21:45:58 -0700
From: Sander Temme <sc...@covalent.net>
Reply-To: dev@httpd.apache.org
To: dev@httpd.apache.org
Subject: Re: where to describe critical OS-specific requirements
> 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?
Here.
> * 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
$linkopts'
#archive_expsym_cmds="$archive_cmds"' && strip -s $export_symbols $lib'
hardcode_direct=yes
...to 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
http://www.apache.org/~pier/macosx/Patches/libtool-1.4.2.patch.gz
But this requires a user-installed patch upon a user-installed libtool. I'm
in favour of the first option.
S.
--
Covalent Technologies sctemme@covalent.net
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
=======================================================
Re: where to describe critical OS-specific requirements
Posted by Cliff Woolley <jw...@virginia.edu>.
On Tue, 9 Apr 2002, Sander Temme wrote:
> Not that simple. ):
> Libtool 1.3.4
Crrrraaaaap!! I was sure it was 1.3.5 on icarus. Sheesh. Alright, I
give up. :)
--Cliff
--------------------------------------------------------------
Cliff Woolley
cliffwoolley@yahoo.com
Charlottesville, VA
Re: where to describe critical OS-specific requirements
Posted by Sander Temme <sc...@covalent.net>.
> Can we *please* apply this patch to the libtool on icarus?? That would
> make the lives of we httpd'ers sooooo much easier...
Not that simple. ):
Libtool 1.3.4 doesn't know anything about Darwin, so it'll only build static
libraries on that platform. There is more to Darwin support in GNU libtool
than this one line patch.
My preferred approach would be, to point users at the patch I posted earlier
and tell them to run buildconf before building. With a working binary build
available, we can ask users to take that extra step before building.
Meanwhile, they can harsh upon Apple for a working libtool in the Developer
Tools. In a similar fashion, it would be nice to have a more recent libtool
on the roll box. This wouldn't help the present Darwin situation though.
S.
--
Covalent Technologies sctemme@covalent.net
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
=======================================================