On Thu, Aug 07, 2003 at 08:12:44AM -0700, Stas Bekman wrote: > >>Peter, can you please give a try to the latest cvs. Thanks. > > > > > >Works fine for me. > > Cool. Do you now specify MP_APR_CONFIG option now?
No, I didn't need to. I use:
perl Makefile.PL MP_APXS=`which %{apxs}` MP_CCOPTS="$(%{apxs} -q CFLAGS)"
make OPTIMIZE=
where %{apxs} is defined
%define apxs apxs2
in the spec file.
> Also can you please explain why /usr/sbin/apxs2 and /usr/bin/apr-config
> don't live under the same tree? I fail to see what it has to do with FHS
> compliancy. The two are quite related in my mind.
That's a very good question.
A default installation of apache2 puts all binaries into $PREFIX/bin, and it
would look like overkill if it would create bin as well as sbin under $PREFIX.
In config.layout we read:
prefix: /usr/local/apache2
exec_prefix: ${prefix}
bindir: ${exec_prefix}/bin
sbindir: ${exec_prefix}/bin
But in most other layouts that can be choosen, there will be different
bin and sbin directories defined, e.g. this is what I use:
exec_prefix: /usr
bindir: ${exec_prefix}/bin
sbindir: ${exec_prefix}/sbin
The simple reason why apxs ends up in sbindir is that apache2's
support/Makefile.in installs it there, while srclib/apr/Makefile.in
installs apr-config into the bindir. I would agree that apxs should
rather go into the bindir. Debian has a patch that moves it there.
Peter
--
Thought is limitation. Free your mind.
pgp00000.pgp
Description: PGP signature
