OK, all seems to have returned to normality, though I have absolutely no idea how/why...
david ----- Original Message ----- From: "David Reid" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, January 11, 2002 12:40 PM Subject: Re: mod_include??? > FWIW, I've just done an update and build on beos and have the same problem, > this time with mod_access. Either I've got something screwy in my build > tree's or Houston, we have a problem. > > david > > ----- Original Message ----- > From: "David Reid" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, January 11, 2002 10:53 AM > Subject: Re: mod_include??? > > > > Following Will's advise to do a make clean;make failed to correct the > > problem. > > > > Here is what i did... > > > > cvs update -dP > > ./buildconf > > ./configure ... > > make clean;make > > rm -rf /usr/local/apache2/* > > make install > > cd /usr/local/apache2/bin > > ./apachectl start > > > > And the result? > > > > httpd: module "mod_include.c" is not compatible with this version of > Apache. > > Please contact the vendor for the correct version. > > > > This has only been happenning since I last updated (3 days ago). > > > > david > > > > ----- Original Message ----- > > From: "David Reid" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Friday, January 11, 2002 9:27 AM > > Subject: mod_include??? > > > > > > > Just done a cvs update/buildconf/make/make install and I'm seeing an > error > > > message that mod_include.c is not compatible with this version of > apache! > > > > > > Anyone any ideas? > > > > > > david > > > > > > > > > > > >
