Apache install on Slackware
 

Hi everyone, having a problem with installing apache from source.

I did a base install of slackware 13 with no X for a test server.

Now when i download and extract apache i run the command "./configure --prefix=/home/httpd --enable-modules=so" i get the output 'Configuring Apache Portable Runtime Utility library...

checking for APR-util... reconfig
configure: error: Cannot use an external APR with the bundled APR-util"

even if i run --with-included-apr at the end of the command i get "checking for C compiler default output file name...
configure: error: in `/usr/local/src/httpd-2.2.11/srclib/apr':
configure: error: C compiler cannot create executables
See `config.log' for more details.
configure failed for srclib/apr"

any help would be very grateful

Thanks

You have to install apr-util package
BTW, why install apache from source ?

For gcc error, make sure you installed mostly all packages in /d slackware directory

and also glibc (not glibc-solibs)

This.

Slackware comes with Apache. Why not use the pre-built package?

Guys thanks for the replies.

I did install apache from the package instead in the end. I suppose i just wanted to jump in the deep end and learn how to install things from source rather going for the easy way out. I might uninstall and try again.

You guys might be shouting/tuting/shaking your heads at your screen thinking why are you doing that, if there's other software you may suggest for me to install from source rather than apache would be grateful for any suggestions.

Just a newbie trying to learn the system i guess

Thanks

You could start with something small like yad.

You have to install:
apr-util
apr-util-devel packages.

Another thing is that the solution was to pass it the following during configure:

# SSL_BASE=../openssl-0.9.7a/ EAPI_MM=../mm-1.2.1/ ./configure --prefix=<path-to-apache> --enable-module=ssl --enable-module=so --with-included-apr

Great stuff! thanks lads

Not with Slackware, libs aren't split into runtime and developer versions.

By the way, the Slackware way is not to install from source, but to compile the code and make a package from it. Also true for most other distributions.

@TobiSGD. Thanks, I don't mean to be annoying but why do most tutorials show you to install from source rather a package?

Installing from source is rather easy (configure && make && make install) and more or less the same in any distribution, correctly making a package needs a bit more. On Slackware it is easy using its packaging tools, but making correct packages for Debian or RedHat is more complicated.
If they want to show the correct way in their tutorials they would have to include tutorials for every distribution out there.

@TobiSGD. Suppose I guess when you know how. I downloaded slack dvd iso, logged into as root, partitioned the drives and then ran setup and followed the basic install. I havent loaded anything since yet. I have been advised to install most of d from slackware. I take that this is whats needed to install and compile from source?

Actually, if you are new to Slackware, it is recommended to do a full install, then you have all the dependencies, all that is needed to compile from source and all that is needed to make and install packages.
There are several good guides for making Slackware packages on the net, you should also read the SlackBook.

---------- Post added 14th Feb 2012 at 20:41 ----------

Actually, if you are new to Slackware, it is recommended to do a full install, then you have all the dependencies, all that is needed to compile from source and all that is needed to make and install packages.
There are several good guides for making Slackware packages on the net, you should also read the SlackBook.

So do your recommend I reinstall the OS or shall I try add the dependencies manually?

It's up to you but if I were you I'd go with the full installation. It's quicker and much more straight forward. It lets you focus on eg. configuring apache straight away.