login
Search
make install recursive error
i can't solve this installation problem
i install the apache web server in linux OS
i can't install apache web server.
I install this server, that message to show me "make install recursive error"
Why a source install?
Source installs are time consuming, and for most people the packaged versions that come with their distro. work well. For example, in Debian: "apt-get install apache2".
Also, on a Linux web server, you might want LAMP (Linux, Apache, MySQL, PHP), or LAPP (Linux, Apache, PostGres SQL, Perl), etc.. This can be done in less than 5 minutes with Debian or other package-based distros: "apt-get install apache2 php5 mysql", for example; it will take much longer than that to install all of this from source since we may have to build dependent libraries as well. [Unless you are developing a GPL application to give back to the community, the MySQL dual-license scheme requires a license fee of $600 USD per server to distribute non-GPL applications; that is why PostGres SQL should be considered].
The packaging system means Apache, etc. will can be updated very easily ("apt-get upgrade"); from source you will need to download/configure/make/make install. Imagine if your web server is in production and this "make install" fails on an upgrade!
Building PHP from source may be necessary to get some features that are not packaged in distro. PHP packages.
Sometimes 64-bit packages are slow to arrive, if your distro. doesn't have them for something like apache (possibly the number one installed item in Linux), that says something about your choice of distro.
If source installations are necessary, some distributions also have source packages that tend to build and install without issue,however, they are rarely as current as the generic source code of the upstream components.
Source installs are time
Source installs are time consuming, and for most people the packaged versions that come with their distro. work well. For example, in Debian: "apt-get install apache2".
Just because something is easy, doesn't mean we should always do it.
The packaging system means Apache, etc. will can be updated very easily ("apt-get upgrade"); from source you will need to download/configure/make/make install. Imagine if your web server is in production and this "make install" fails on an upgrade!
Just imagine if your web server is in production and this "apt-get install apache2" fails on an upgrade! (to reverse what you said)
If you are doing production systems, you will have a box that is set aside somewhere and
you test all the upgrades on it first, then if everything is ok, you do the upgrade on the
real server. Or you could keep both boxes exactly the same, then when you do the upgrade on
the test server (and everything is ok after doing tests), you swap them round and your test
server becomes the new production system. There are no doubt other ways to do it also.
But you should not find yourself in a situation where you just borked your production system,
wheter you use source tarballs or packages.