----------
From: Rob Donnellan rob.donnellan@mci.com
To: Java Apache Users java-apache-users@list.working-dogs.com
Subject: Re: Jserv - Apache DSO support problem -
Date: Mon, Mar 8, 1999, 7:04 AM

i had this problem on redhat 5.2.  for me the message came up because
the apxs module was missing in the redhat rpm of apache.  the
configure.in file checks for apxs if you use the --with-apache-install
option, if apxs is not there then you get 
'checking for Apache directory... configure: error: does not have DSO
support'
i installed apache 1.3.4 (default layout) with dso support
(--enable-module=so --enable-shared=max) and got the apxs module in the
right place, then the jserv config worked.

Jian Sun wrote:
> 
> Hello,
> 
> I am trying to install Jserv 1.0b3 with Apache 1.3.4 on Solaris 2.5.1 but 
meet the DSO support problem.
> 
> Here are steps I have done:
> 
> First compile Apache 1.3.4 with DSO support:
> ./configure --prefix=/www --enable-rule=SHARED_CORE --enable-module=so
> then
> make install
> 
> Upto now, everything seems ok. The compiled file go to /www/libexec and /www/bin.
> 
> Now try to make Jserv module after change to the directory Apache by typing:
> ./configure --with-apache-install=/www
> 
> The error message comes out like:
> loading cache ./config.cache
> checking for a BSD compatible install... src/scripts/build/unix/install-sh -c
> checking whether build environment is sane... yes
> checking whether make sets ${MAKE}... (cached) yes
> checking for working aclocal... found
> checking for working autoconf... found
> checking for working automake... found
> checking for working autoheader... found
> checking for working makeinfo... missing
> ********* (skipped many lines)
> checking host system type... sparc-sun-solaris2.5.1
> checking for java... (cached) /usr/local/etc/jdk1.1.5/bin/java
> checking for javac... (cached) /usr/local/etc/jdk1.1.5/bin/javac
> checking for jar... (cached) /usr/local/etc/jdk1.1.5/bin/jar
> checking for Apache directory... configure: error: does not have DSO support
> 
> Can anyone give me hints what I missed here?
> 
> Appreciate your help.
> 
> Jian

Answers in this category:

From: David Smith kb7psn@jps.net
Date: May 4, 1999    8:11:00 PM PDT

Try the Apache server re-configure again,
this time setting a "--prefix=$prefix" value
(with a properly substituted $prefix value).

For the particular error encountered, the
Apache server version of the "./src/support/apxs"
perl script didn't completely substitute the values
on the following lines :

78:my $CFG_PREFIX        = '@prefix@';        # substituted via APACI install
79:my $CFG_SBINDIR       = '@sbindir@';       # substituted via APACI install
80:my $CFG_INCLUDEDIR    = '@includedir@';    # substituted via APACI install
81:my $CFG_LIBEXECDIR    = '@libexecdir@';    # substituted via APACI install
82:my $CFG_SYSCONFDIR    = '@sysconfdir@';    # substituted via APACI install

Thus, when the "$CFG_SBINDIR/$CFG_TARGET" within
 the "apxs" script gets expanded, the result is
not a valid path name under the OS and the error
gets produced.

I had to do a little more work to install JServ 1.0 into a previously installed
Apache 1.3.6:

1. Patch /usr/local/apache/bin/apxs to use $CFG_PREFIX on all directories.

my $CFG_SBINDIR       = $CFG_PREFIX.'/bin';       # substituted via APACI install
my $CFG_INCLUDEDIR    = $CFG_PREFIX.'/include';    # substituted via APACI install
my $CFG_LIBEXECDIR    = $CFG_PREFIX.'/libexec';    # substituted via APACI install
my $CFG_SYSCONFDIR    = $CFG_PREFIX.'/conf';    # substituted via APACI install

I know this should be fixed when the server is built, but I wanted to use only
the binary distribution I already had set up. (It might ultimately be a bit
tidier if $CFG_PREFIX included a trailing '/' so one would not need to include
it in every path appended to it.)

2. Fix Apache_JServ_1.0/configure.in

Replace references to ${withall}/sbin/apxs with ${withall}/bin/apxs

There is no sbin directory in the 1.3.6 distribution I had already installed and
apxs was in the bin directory anyway.

3. Fix Apache_JServ_1.0/configure.in and re-build ./configure with autoconf:

Where it says "Feel free to fix my lameness" ... I changed it to make the tar
operation conditional upon using a source distribution:

if [ x$apache_dir_is_src = xtrue ] ; then
    (cd $apche_dir/src/modules/jserv...
fi

Otherwise configure dies when it tries to copy files to a non-existent place if
you are using an installed server. I have not tested this change with a source
distribution.

With these changes the configure script finally (after much hair pulling)
created the correct makefiles to build mod_jserv.so without requiring a
source distribution of the server. After following the rest of the configuration
steps the Hello applet worked as advertised.

There is alittle bug in the Install of Apache-Jserv DSO.
If you have compiled you Apache with DSO and have tried to install
JServ with DSO and the install script reads "you do not have DSO SUPPORT"
Check your perl version.  You MUST have perl 5.0.  The incorrect error message 
cost me days of headache.

Merdock