Ruediger Pluem wrote:
On 06/20/2008 04:49 PM, [EMAIL PROTECTED] wrote:
Author: wrowe
Date: Fri Jun 20 07:49:22 2008
New Revision: 669920
URL: http://svn.apache.org/viewvc?rev=669920&view=rev
Log:
AC_USE_SYSTEM_EXTENSIONS encompases _MINIX and _AIX and
silences autoconf 2.62
Modified:
httpd/httpd/branches/2.2.x/configure.in
Sorry for being confused, but why are these changes not RTC?
They can be, if you like. I'm not fond of discovering that the build
against a --with-ssl= path blows up completely once you salt it with
zlib compression (kerberos, resolv etc) on platforms with satisfy all
symbols in effect. Worked quite nicely back in my good old days of
openssl 0.9.7, and I then discovered nobody considered actually fixing
our stable branch with the corrections on trunk.
Of course it picked up pkg-config testing of the wrong openssl.pc at
the wrong place in the configure script, and my rage at the build
system proceeded from there. If a necessary patch can sit back for
2.5 years, that's a problem.
In short, it's fallen into disrepair. At this point only one flaw
remains, and that's the nested pcre crying out during ./buildconf.
Even looked for a switch option to silence it, but autoheader won't
agree to shut up.
So I treated this set of changes as build schema changes as I would
on Win32, where people equally ignore how the schema will impact any
build except their own. But if someone with more Autoconf-foo than I(*)
would like to actually challenge the changes, or find a single flaw,
I'm all set to be beaten up over them. Fire away(**).
Bill
(*) clear from a number of issues that autoconf patches are not reviewed
by any httpd'ers, autoconf is simply bludgeoned into submission
(**) yes, I'm grumpy today
