Hi,

I am running Slackware 10.2 and am wanting to install Apache 2.2. My
machine currently has a clean install and does not have Apache 1.3
installed.

I have downloaded the tar.gz file from the Apache website and have been
following their installation instructions, found here:

http://httpd.apache.org/docs/2.2/install.html

I added the following layout to the config.layout file:

<Layout Slackware>
prefix: /usr
exec_prefix: ${prefix}
bindir: ${prefix}/bin
sbindir: ${prefix}/sbin
libdir: ${prefix}/lib
libexecdir: ${prefix}/lib/apache2
mandir: ${prefix}/man
sysconfdir: /etc/apache2
datadir: /var/www
iconsdir: ${datadir}/icons
Building Apache2 1
htdocsdir: ${datadir}/htdocs
manualdir: ${datadir}/manual
cgidir: ${datadir}/cgi−bin
includedir: ${prefix}/include/apache2
localstatedir: /var
runtimedir: ${localstatedir}/run
logfiledir: ${localstatedir}/log/apache2
proxycachedir: ${localstatedir}/cache/apache2
infodir: ${exec_prefix}/share/info
installbuilddir: ${datadir}/build
errordir: ${datadir}/error
</Layout>

I then called ./configure --enable-layout=Slackware --enable-module=most
--enable-mods-shared=most

After which I called make and then make install

make install does not seem to finish however and it displays the
following error message at the end of its output:

/usr/bin/ginstall: too few arguments
Try `/usr/bin/ginstall --help' for more information.
/usr/bin/ginstall -c -m 755
/global/software/apache2/httpd-2.2.0/srclib/apr/build/mkdir.sh
/usr/bin/ginstall: too few arguments
Try `/usr/bin/ginstall --help' for more information.
make[2]: *** [install] Error 1
make[2]: Leaving directory `/global/software/apache2/httpd-2.2.0/srclib/apr'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/global/software/apache2/httpd-2.2.0/srclib'
make: *** [install-recursive] Error 1

I ran /usr/bin/ginstall --help for more information but am stuck with
what I have to do with this. Where abouts is this been called in the
make install process, how do I modify its call so there are the correct
amount of arguments and what I missing anyway?

Would appreciate any help on this as I am eager to get apache2 installed
so that I get on with my other tasks

Thanks in advance

Andrew

Andrew Peters wrote:
> Hi,
>
> I am running Slackware 10.2 and am wanting to install Apache 2.2. My
> machine currently has a clean install and does not have Apache 1.3
> installed.
I install Apache 2.x in /usr/local (so it does not get overwritten by a
Slackware install); works just fine. Here's the config.nice that builds it:

#! /bin/sh
#
# Created by configure
"configure" \
"--enable-modules=most" \
"--enable-mods-shared=max" \
"--enable-ssl" \
"$@"

You really don't need all the other arguments; this will do the
configure, then you make, make install -- it'll be in /usr/local/apache2.

If you want to add PHP (also in /usr/local, also for the same reason),
here's the config.nice for that:

#! /bin/sh
#
# Created by configure
'configure' \
'--with-apxs2=/usr/local/apache2/bin/apxs' \
'--with-mysql' \
"$@"

If you don't want to install in /usr/local (trust me, that's the
easiest), add the "prefix" and other arguments to the above. Apache 2.x
and PHP are running on five production machines as above, no problems
whatsoever.

--
Everything works -- if you let it.

Hi Thanks for your reply,

Just a few questions however.

When you say 'does not get overwritten by a Slackware install', are you
referiing to upgrading slackware. Also does this mean that you are
using the default apache layout?

I am a bit confused aswell as to how this is going to fix my problem, as
the error message that I received complained of the following:

/usr/bin/ginstall: too few arguments

Surely installing into another directory is not the answer for fixing
this? Is it?

Andrew


Thomas Ronayne wrote:
> Andrew Peters wrote:
>
>> Hi,
>>
>> I am running Slackware 10.2 and am wanting to install Apache 2.2. My
>> machine currently has a clean install and does not have Apache 1.3
>> installed.
>
> I install Apache 2.x in /usr/local (so it does not get overwritten by a
> Slackware install); works just fine. Here's the config.nice that builds it:
>
> #! /bin/sh
> #
> # Created by configure
> "configure" \
> "--enable-modules=most" \
> "--enable-mods-shared=max" \
> "--enable-ssl" \
> "$@"
>
> You really don't need all the other arguments; this will do the
> configure, then you make, make install -- it'll be in /usr/local/apache2.
>
> If you want to add PHP (also in /usr/local, also for the same reason),
> here's the config.nice for that:
>
> #! /bin/sh
> #
> # Created by configure
> 'configure' \
> '--with-apxs2=/usr/local/apache2/bin/apxs' \
> '--with-mysql' \
> "$@"
>
> If you don't want to install in /usr/local (trust me, that's the
> easiest), add the "prefix" and other arguments to the above. Apache 2.x
> and PHP are running on five production machines as above, no problems
> whatsoever.
>

Andrew Peters wrote:
> Hi Thanks for your reply,
>
> Just a few questions however.
OK
>
> When you say 'does not get overwritten by a Slackware install', are
> you referiing to upgrading slackware. Also does this mean that you are
> using the default apache layout?
Yeah, I was referring to upgrade but that's probably moot because
Slackware won't upgrade if package information is not present in
/var/log/packages. And yes, I am using the default Apache layout
(because I find it much, much simpler to administer multiple systems
[including Slackware and Solaris] that way).

The "Slackware layout" for Apache 1.x really doesn't apply to Apache 2.x
and your ginstall error may just be the result of trying to build with
it, you'd have to look through the build to see specifically why. It
looks like you're trying to use a modified slackbuild script (could be
wrong, but the "enable-layout Slackware" is a hint).
>
> I am a bit confused aswell as to how this is going to fix my problem,
> as the error message that I received complained of the following:
Here's the thing -- the config.nice programs? They work; i.e., you'll
get a fully-usable Apache 2.x with Apache 2.x's default layout installed
in Apache's default location (which is /usr/local/apache2) rather than
spread all over the place like the Slackware Apache 1.x installation
(and you can get on with life rather than fighting with the thing). It
really does not matter "where" the thing lives, it only matters that it
does what it's supposed to do without bothering you -- you can make
symbolic links from webish applications; e.g., Bugzilla, into
/usr/local/apache2/htdocs and all is right with the world.

I only come at these kind of things with one thought in mind: the Apache
folks knows more about this that I do and if they default to a given
location and layout, well, who am I to argue. I like easy instead of
reinventing the wheel all the time. I don't like spending hours or days
fooling around trying to make something work -- I have neither the time
nor the desire any more. Easy is good, hard is bad. Everything in one
tree is good, spread all over is bad. Simple is good, complicated is a
pain. Don't like /usr/local? Prefix it with /opt (or wherever you'd like
-- it is Linux, after all).

It's up to you, but I'd give the default a shot and see what happens.
You can always change it later.

--

Everything works -- if you let it.