Quoting Emiliano <[EMAIL PROTECTED]>:
> Chen Shiyuan wrote:
>
> > > That would work but these header files really should be where
> > > apxs says they are.
> >
> > Hmm... somehow when I compiled and did a make install from the
> > apache-1.3.12 source tarballs, it left the files in the source
> directory
> > and didn't copy over to the /usr/local/apache directory.
> >
> > I have resorted to manually copying all the .h files over to
> the
> > /usr/local/apache/include directory.
>
> Was there anything at all in that directory?
It was empty. I don't know why it was empty previously but I was trying
to do a fresh installation of apache scratch from the tarballs today and
it actually copied files into the /usr/local/apache/include directory.
> > BTW, do you have any idea what else is required to make php3
> coexist with
> > php4? I basically compiled them using
> > --with-apxs=/usr/local/apache/bin/apxs and also
> --enable-versioning. and
> > "make install" threw them into the /usr/local/apache/libexec
> directory.
>
> I haven't used versioning myself
I see... but now I think I am facing a very strange problem with modules
which I do not suspect that it is anyhow related to midgard but it will
definitely set back my attempts at midgard indefinitely until I get this
sorted out.
It appears that when I try to compile PHP4.01pl2/4.02 as a module using
--with-apxs=/usr/local/apache/bin/apxs, my httpsd binary cannot start
anymore (the httpsd binary is compiled WITHOUT PHP built in). It will
just segfault. But the moment I compile PHP4 into my httpsd binary
statically, it will work just fine. The apache config file remained
unchanged throughout other than just adding in the Load/Addmodule lines.
Oh no... times are bad...
Thanks for your all assistance till date...
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
