httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Havard" <>
Subject Re: alpha4
Date Tue, 06 Jun 2000 03:02:47 GMT
On Mon, 5 Jun 2000 09:48:11 -0700 (PDT), wrote:

>> >That value is only supposed to be cached if it isn't specified, and it is
>> >specified if you turn on mod_so.  The problem is that the
>> >config.m4.  Moving this handles the problem with, but not
>> >some of the other stuff.  The fix is on the way.
>> I encountered the problem while building APR standalone. After a distclean
>> I ran "configure", then "configure --enable-dso". DSO didn't get enabled.
>> Deleting config.cache and re-"configure --enable-dso"-ing DID enable DSO.
>This I don't understand.  If you look at the Autoconf code that deals with
>DSO support, we check the command like for an argument that specifically
>deals with dso (--enable-dso or --disable-dso), if neither of these are
>found we check the cache.  There was a mistake in the very first
>implementation of --enable-dso, but it was changed the day after
>enabling/disabling support was added.  When did you attempt this
>stuff?  Is there potentially a bug in OS/2's autoconf?  I am absolutely
>stimied by this, so I am graspiong at straws.

Sorry, this happened to me a couple of days ago but now seems to be fixed.
I guess I didn't spot the patch....

 |  Brian Havard                 |  "He is not the messiah!                   |
 |  |  He's a very naughty boy!" - Life of Brian |

View raw message