Greg Stein <[EMAIL PROTECTED]> writes:
> No. apr_hints is a last resort. Actual tests like the AC_TRY_COMPILE() that
> Justin did are the right way to do it. We should always try to avoid
> hard-coding conditions to the host/library/whatever and *test* for them
> instead.
>
> autoconf was written to use the testing approach, rather than the "know
> everything about all platforms" approach that Apache 1.3 used. apr_hints is
> left over from the 1.3 days; ideally, we would find tests that would remove
> every single one of those hints.
Which of the text below do you disagree with?
Jeff said previously:
>Any kind of libc feature test macros need to be turned on ASAP,
>because they could influence the outcome of other tests (whether or
>not we find an interface or which flavor of an interface we find).
>I don't think we can wait until this point in autoconfiguration to
>start turning on libc feature test macros. Maybe it will work on
>some glibc version with the current set of tests, but I don't think it
>is cool in general. It seems to me that as soon as you change libc
>feature test macros you need to start over at ground zero.
--
Jeff Trawick | [EMAIL PROTECTED] | PGP public key at web site:
http://www.geocities.com/SiliconValley/Park/9289/
Born in Roswell... married an alien...
