How do I find out if DSO support is avaialable?

How do I find out if DSO support is avaialable?

Post by Valentine Ananthara » Fri, 23 Jul 1999 04:00:00



Greetings!

I downloaded and installed a pre-compiled version for Irix 6.2.

Is there a utility to help me find out if this compiled version
supports DSO?  (I have been trying to install jserv, and the
config script tells me that there is not DSO support.)

Thanks.

VGA

 
 
 

How do I find out if DSO support is avaialable?

Post by Valentine Ananthara » Fri, 23 Jul 1999 04:00:00


I forgot to mention that I am referring to the Apache web server
version 1.3.6.  Sorry about that.

VGA


> Greetings!

> I downloaded and installed a pre-compiled version for Irix 6.2.

> Is there a utility to help me find out if this compiled version
> supports DSO?  (I have been trying to install jserv, and the
> config script tells me that there is not DSO support.)

> Thanks.

> VGA


 
 
 

How do I find out if DSO support is avaialable?

Post by Valentine Ananthara » Fri, 23 Jul 1999 04:00:00


Jim,

This is what I get from 'httpd -l'

     Compiled-in modules:
       http_core.c
       mod_so.c

So what does this mean?  I know that I am using mod_rewrite and use
the LoadModule directive.  Does this mean that it has DSO support?
Then I wonder why jserv config script complains and refuses to
compile and install.

VGA



> :I forgot to mention that I am referring to the Apache web server
> :version 1.3.6.  Sorry about that.

> What does running httpd -l say?
> --
> Jim Davis              | "Professor!  You turned it down again!!"


 
 
 

How do I find out if DSO support is avaialable?

Post by Joshua Sliv » Fri, 23 Jul 1999 04:00:00



> Jim,
> This is what I get from 'httpd -l'
>      Compiled-in modules:
>        http_core.c
>        mod_so.c
> So what does this mean?  I know that I am using mod_rewrite and use
> the LoadModule directive.  Does this mean that it has DSO support?

Yes.

Quote:> Then I wonder why jserv config script complains and refuses to
> compile and install.

Because you are doing something wrong?  People might have more luck
helping you if you said exactly what you have done and exactly
what the error messages are.

--
Joshua Slive

http://finance.commerce.ubc.ca/~slive/

 
 
 

How do I find out if DSO support is avaialable?

Post by Valentine Ananthara » Sat, 24 Jul 1999 04:00:00




> > Jim,

> > This is what I get from 'httpd -l'

> >      Compiled-in modules:
> >        http_core.c
> >        mod_so.c

> > So what does this mean?  I know that I am using mod_rewrite and use
> > the LoadModule directive.  Does this mean that it has DSO support?

> Yes.

Thanks -- at least we have now determined that my apache installation
does have DSO support.

Quote:> > Then I wonder why jserv config script complains and refuses to
> > compile and install.  An example configure line for DSO compilation
> is:

> Because you are doing something wrong?  People might have more luck
> helping you if you said exactly what you have done and exactly
> what the error messages are.

This is what the jserv doscumentation says about DSO install for apache:

     ./configure \
                     --prefix=/usr/local/jserv \
                     --with-apache-install=/usr/local/apache \
                     --with-jdk=home=/path/to/jdk \
                     --with-jsdk=/path/to/jsdk \
                     --disable-debugging

But, when I try it, this is what I get:

     # ./configure --prefix=/usr/local/apache/jserv
     --with-apache-install=/usr/local/apache
     --with-jdk=home=/usr/java
     --with-jsdk=/usr/local/apache/lib/jsdk.jar
     loading cache ./config.cache
     Configuring ApacheJServ/1.0
     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... missing
     checking for working autoconf... missing
     checking for working automake... missing
     checking for working autoheader... missing
     checking for working makeinfo... missing
     checking host system type... mips-sgi-irix6.2
     checking for ranlib... (cached) :
     checking for gcc... (cached) gcc
     checking whether the C compiler (gcc  ) works... yes
     checking whether the C compiler (gcc  ) is a cross-compiler...
     no
     checking whether we are using GNU C... (cached) yes
     checking whether gcc accepts -g... (cached) no
     checking for ld used by GCC... (cached)
     /usr/local/lib/gcc-lib/mips-sgi-irix5/2.6.3/ld
     checking if the linker
     (/usr/local/lib/gcc-lib/mips-sgi-irix5/2.6.3/ld) is GNU ld...
     (cached) no
     checking for BSD-compatible nm... (cached) /usr/bin/nm -B
     checking whether ln -s works... (cached) yes
     checking for gcc option to produce PIC... none
     checking if gcc static flag -static works... -static
     checking if the linker
     (/usr/local/lib/gcc-lib/mips-sgi-irix5/2.6.3/ld -32) is GNU
     ld... no
     checking whether the linker
     (/usr/local/lib/gcc-lib/mips-sgi-irix5/2.6.3/ld -32) supports
     shared libraries... yes
     checking command to parse /usr/bin/nm -B output... yes
     checking how to hardcode library paths into programs...
     immediate
     checking for /usr/local/lib/gcc-lib/mips-sgi-irix5/2.6.3/ld
     -32 option to reload object files... -r
     checking dynamic linker characteristics... irix6.2 ld.so
     checking if libtool supports shared libraries... yes
     checking whether to build shared libraries... yes
     checking whether to build static libraries... no
     checking for objdir... .libs
     creating libtool
     checking whether make sets ${MAKE}... (cached) yes
     checking for a BSD compatible install...
     src/scripts/build/unix/install-sh -c
     checking whether ln -s works... (cached) yes
     checking for gcc... (cached) gcc
     checking whether the C compiler (gcc -O2 ) works... yes
     checking whether the C compiler (gcc -O2 ) is a
     cross-compiler... no
     checking whether we are using GNU C... (cached) yes
     checking whether gcc accepts -g... (cached) no
     checking for working const... (cached) yes
     checking how to run the C preprocessor... (cached) gcc -E
     checking for ANSI C header files... (cached) yes
     checking for mode_t... (cached) yes
     checking whether time.h and sys/time.h may both be included...
     (cached) yes
     checking whether struct tm is in sys/time.h or time.h...
     (cached) time.h
     checking for ANSI C header files... (cached) yes
     checking for gettimeofday... (cached) yes
     checking for java in /usr/java/bin... /usr/java/bin/java
     checking for javac in /usr/java/bin... /usr/java/bin/javac
     checking for jar in /usr/java/bin... /usr/java/bin/jar
     checking for Apache directory... configure: error:  does not
     have DSO support

I noticed that the configure script was looking for
/usr/local/apache/sbin/apxs, and since I did not have the sbin/
directory I created one and copied apxs into /usr/local/apache/apxs --
and I still got the same error that my apche installation does not have
DSO support.

Appreciate any help in resolving this.

Thanks.


 
 
 

How do I find out if DSO support is avaialable?

Post by amacka.. » Wed, 28 Jul 1999 04:00:00


Valentine,

I had the same problem.  Make sure that you have Perl installed and
working properly.  View the first line of 'apxs' to make sure Perl
path is setup ok (apxs is a Perl script).  Try running 'apxs' from
the command prompt to see if it gives an error when running.

Andrew Mackay





> > > Jim,

> > > This is what I get from 'httpd -l'

> > >      Compiled-in modules:
> > >        http_core.c
> > >        mod_so.c

> > > So what does this mean?  I know that I am using mod_rewrite and
use
> > > the LoadModule directive.  Does this mean that it has DSO support?

> > Yes.

> Thanks -- at least we have now determined that my apache installation
> does have DSO support.

> > > Then I wonder why jserv config script complains and refuses to
> > > compile and install.  An example configure line for DSO
compilation
> > is:

> > Because you are doing something wrong?  People might have more luck
> > helping you if you said exactly what you have done and exactly
> > what the error messages are.

> This is what the jserv doscumentation says about DSO install for
apache:

>      ./configure \
>                      --prefix=/usr/local/jserv \
>                      --with-apache-install=/usr/local/apache \
>                      --with-jdk=home=/path/to/jdk \
>                      --with-jsdk=/path/to/jsdk \
>                      --disable-debugging

> But, when I try it, this is what I get:

>      # ./configure --prefix=/usr/local/apache/jserv
>      --with-apache-install=/usr/local/apache
>      --with-jdk=home=/usr/java
>      --with-jsdk=/usr/local/apache/lib/jsdk.jar
>      loading cache ./config.cache
>      Configuring ApacheJServ/1.0
>      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... missing
>      checking for working autoconf... missing
>      checking for working automake... missing
>      checking for working autoheader... missing
>      checking for working makeinfo... missing
>      checking host system type... mips-sgi-irix6.2
>      checking for ranlib... (cached) :
>      checking for gcc... (cached) gcc
>      checking whether the C compiler (gcc  ) works... yes
>      checking whether the C compiler (gcc  ) is a cross-compiler...
>      no
>      checking whether we are using GNU C... (cached) yes
>      checking whether gcc accepts -g... (cached) no
>      checking for ld used by GCC... (cached)
>      /usr/local/lib/gcc-lib/mips-sgi-irix5/2.6.3/ld
>      checking if the linker
>      (/usr/local/lib/gcc-lib/mips-sgi-irix5/2.6.3/ld) is GNU ld...
>      (cached) no
>      checking for BSD-compatible nm... (cached) /usr/bin/nm -B
>      checking whether ln -s works... (cached) yes
>      checking for gcc option to produce PIC... none
>      checking if gcc static flag -static works... -static
>      checking if the linker
>      (/usr/local/lib/gcc-lib/mips-sgi-irix5/2.6.3/ld -32) is GNU
>      ld... no
>      checking whether the linker
>      (/usr/local/lib/gcc-lib/mips-sgi-irix5/2.6.3/ld -32) supports
>      shared libraries... yes
>      checking command to parse /usr/bin/nm -B output... yes
>      checking how to hardcode library paths into programs...
>      immediate
>      checking for /usr/local/lib/gcc-lib/mips-sgi-irix5/2.6.3/ld
>      -32 option to reload object files... -r
>      checking dynamic linker characteristics... irix6.2 ld.so
>      checking if libtool supports shared libraries... yes
>      checking whether to build shared libraries... yes
>      checking whether to build static libraries... no
>      checking for objdir... .libs
>      creating libtool
>      checking whether make sets ${MAKE}... (cached) yes
>      checking for a BSD compatible install...
>      src/scripts/build/unix/install-sh -c
>      checking whether ln -s works... (cached) yes
>      checking for gcc... (cached) gcc
>      checking whether the C compiler (gcc -O2 ) works... yes
>      checking whether the C compiler (gcc -O2 ) is a
>      cross-compiler... no
>      checking whether we are using GNU C... (cached) yes
>      checking whether gcc accepts -g... (cached) no
>      checking for working const... (cached) yes
>      checking how to run the C preprocessor... (cached) gcc -E
>      checking for ANSI C header files... (cached) yes
>      checking for mode_t... (cached) yes
>      checking whether time.h and sys/time.h may both be included...
>      (cached) yes
>      checking whether struct tm is in sys/time.h or time.h...
>      (cached) time.h
>      checking for ANSI C header files... (cached) yes
>      checking for gettimeofday... (cached) yes
>      checking for java in /usr/java/bin... /usr/java/bin/java
>      checking for javac in /usr/java/bin... /usr/java/bin/javac
>      checking for jar in /usr/java/bin... /usr/java/bin/jar
>      checking for Apache directory... configure: error:  does not
>      have DSO support

> I noticed that the configure script was looking for
> /usr/local/apache/sbin/apxs, and since I did not have the sbin/
> directory I created one and copied apxs into /usr/local/apache/apxs --
> and I still got the same error that my apche installation does not
have
> DSO support.

> Appreciate any help in resolving this.

> Thanks.



Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
 
 
 

1. Can't find /dev/nst0....What am I doing wrong?

I'm relatively new to linux, so I expect a lot of flames from this
question.  What am I doing wrong with the tar command?  The manual page
tells me absolutely nothing except that I'm supposed to used -x to
retrieve the files in the archive.  Whenever I try tar -x <filename> it
says can't find /dev/nst0, no such device.  However, that device is
there.  Is it a problem with the permissions, the option I chose, or am
I just downright stupid.  Any help would be appreciated.

2. Slackware and Redhat make ninety8 install easy

3. lilo -> DOS WD 32 bit IFS??

4. Writing wrappers ?

5. How to find out application that send outs packets on certain port

6. Q: vim / ansi term type produces color output on Linux, but not Solaris

7. apache DSO problem (Loaded DSO libexec/mod_mime.so uses plain Apache 1.3 API)

8. Floppies under 2.5.

9. Linux program can't find ifs lib file -- help

10. Rebuilding Apache with DSO support

11. Problem with Apache + PHP4 DSO : symbol __muldi3: referenced symbol not found

12. Building Apache 1.3.6 or 1.3.9 with DSO Support on Solaris 2.7

13. Java question -- AWT dso not found