|
|
Posted by Double Echo on 06/26/06 11:39
Lawrence,
I hope the vast majority of the responses didn't discourage you from
coming back here looking for more answers. I was surprised nobody
recommended a better version of the Apache web server. 1.x is so old
now compared to the new versions that you really should install a 2.x
version.
Apache -- http://httpd.apache.org/
Apache 2.2.2 Docs -- http://httpd.apache.org/docs/2.2/new_features_2_2.html
There are a whole host of reasons why you should consider a newer version,
which I won't go into here. The biggest reason you should use a newer
version is the built in support for mod_ssl, and the configs are even easier
now--compared to the dinosaur 1.x version. You should only use the 1.x
version if you have no choice. You will have to add on so many mods to 1.x
it really gets painful.
One other important note, RPM versions, whether on SuSE, RedHat, or other
distro, and .deb versions typically will install Apache in a different
pattern compared to the download version directly from Apache. They will
try to 'help' you by putting the httpd.conf in /etc/httpd and other variations
so that you can find and configure the web server more conveniently. But it
also means that if you want your own version instead of the RPM that you
have to figure out what the RPM command line was that the distro people used
to build apache using the ./config command-line or get it as close as you
can on your own. You are probably better off just installing the default
in /usr/local/apache2, and just having everything in one place until you
can spend the time to mimic the distro version. This also means you will
have to bootstrap Apache on your own, i.e
/usr/local/apache2/bin/apachectl start|stop
which is not a bad thing, but it also means you might end up with two
different versions at bootup. You can overcome this by creating your own
/etc/init.d/Apache2 script, or you can install Webmin and create one in their
interface, and it will also set it up for autostart on machine boot. Then
you can also disable the RPM version from autostarting when your machine
starts up. But this also means if you have other applications that depend
on the RPM Apache, that they may complain on upgrades if Apache isn't in the
RPM database. To overcome this, you can create an RPM of your /usr/local/apache2/
version before installation, then install it as an RPM. I've never done that
so I can't help you on that. I'm somewhat a combination of lazy and a purist
who likes everything under one directory, so I don't split out the config
over to /etc/httpd etc. I'm sure it's just because I'm lazy and afraid I'll
install over something that some other app was depending on and make a mess
of things.
You might also post over in the alt.apache.configuration group, they have
some heavy hitters there.
Hope this helps...
lawrence k wrote:
> I've installed Apache 1.3.36 on my Redhat EL 3 machine. Now I'm trying
> to install PHP 5.1.4. I can not get the ./configure command to work. I
> keep getting this error:
>
> configure: error: Invalid Apache directory - unable to find httpd.h
> under /usr/local/apache/include
>
> So then I run this command:
>
> find / -name httpd.h
>
> which should find every file on my machine with the name "httpd.h".
> These are the results I get:
>
> /usr/local/apache/include/httpd.h
> /home/shelley/apache_1.3.36/src/include/httpd.h
>
> So I've rerun the ./configure command, using this first:
>
> --with-apache=/usr/local/apche/include
>
> and since that didn't work:
>
> --with-apache=/home/shelley/apache_1.3.36/src/include/httpd.h
>
> but I get the "Invalid directory" error with both addresses.
>
> What am I missing?
>
Navigation:
[Reply to this message]
|