Um, as I haven't looked at the source and am unlikely to have a chance to dig
into it for you, I'm wary of leaping in with off-the-top-of-my-head suggestions
... *but* ... :-)
On Tue, 24 Apr 2001, Diana Shepard wrote:
> Thanks very much for the taking the time
> to respond. I tried your suggestion, but
> unfortunately the same error persists. Think
> I'll just have to skip MM in the mod_ssl install.
It looks like the line you replaced is not where the error is occuring, it's
only a line that retrieves the value of an earlier test - ie. it assumes that an
earlier test had succeeded and had deposited the result into the "conftestval"
file. In other words, the failure seems to be occuring earlier.
Ie.
MM_SHM_MAXSEGSIZE="`cat conftestval`"
should populate MM_SHM_MAXSEGSIZE with the text inside "conftestval". Try
looking a line or two higher up to figure out where "conftestval" is actually
created. That seems to be where the configuration process is actually stopping.
I suspect if you stop that test from running (so hopefully the configuration
scripts should get past that point) *and* follow the original suggestion about
hard-coding the value for MM_SHM_MAXSEGSIZE, then you should be OK.
Then again, I could be talking utter garbage too. :-) Good luck.
Cheers,
Geoff
PS: Actually, by fishing about in this, you'll probably get an idea for what's
going wrong as you make these changes. Once it's all up and running (touch
wood), perhaps you could take a look at the offending code and see why it's not
working as intended on your host system? It would be good to submit a fix (or at
least a clear bug description) to Ralf so it can be fixed permanently.
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
