Re: mod_webapp -- EAPI error

[John Clayton]

That's good to know.  Somehow I did get the build to work.  I followed 
your steps,
% ./support/buildconfig.sh
% CFLAGS=-DEAPI ./configure  (on one line)
and then make

worked nicely, copied to /usr/lib/apache and added the right lines to 
httpd.conf.

not sure why it wasn't working before.  The only thing I did different 
was mess with the lineage.

not more complaints about -DEAPI, but it woul dbe nice to know what's up.

John


On Wednesday, December 26, 2001, at 11:57 AM, Cynthia Jeness wrote:

> John,
>
> By searching through Google, I discovered this link to a slightly older 
> set of  RPMS for
> Tomcat including one for mod_webapp:
>
> http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0/rpms/
>
> This is not the link that you get from the Jakarta site.  The Jakarta 
> link ends wiht
> "4.0.1/rpms".
>
> When I installed the 4.0/rpm version of mod_webapp, then my "EAPI" 
> error went away and I
> could load the "HelloWorldExample" servlet.  However, the changes that 
> the RPM made to the
> httpd.conf file seemed to be incorrect.  So I deleted these and added 
> the lines specified
> in the README.txt for mod_webapp.
>
> I would still like to understand  how to compile from source and get an 
> appropriate module
> since it seems like the rpm for mod_webapp is not always provided.  
> Further, some of our
> systems run Apache on Solaris where I need to be able to compile the 
> source.
>
> So, can anyone from the Apache team please help with this issue?
>
> Cynthia
>
>
> John Clayton wrote:
>
>> I have just experienced the very same issue with the binary.  What's
>> more, I can't even get configure to run while trying to build it from
>> source, as it is reporting a syntax error on line 5.  Hmm 
>>
>> On Wednesday, December 26, 2001, at 10:45 AM, Cynthia Jeness wrote:
>>
>>> I got the sources for Apache 1.3.22, compiled and installed.
>>>
>>> Then I got the sources for mod_webapp.  After unpacking, I did the
>>> following as described in the "README.txt" file:
>>>
>>> ./support/buildconf.sh
>>> CFLAGS=-DEAPI \
>>> ./configure --with-apxs=/usr/local/bin
>>>
>>> Then I executed make.  Watching the compiles display on my screen, the
>>> "-DEAPI" flag was specified.
>>>
>>> The sources compiled and "mod_webapp.so" was created.  Then I copied
>>> this module to my Apache modules directory,  modified the httpd.conf 
>>> as
>>> directed in the README.txt and started Apache.  Apache did start, 
>>> but I
>>> received the following warning:
>>>
>>> starting httpd: [Wed Dec 26 09:21:24 2001] [warn] Loaded DSO
>>> modules/mod_webapp.so uses plain Apache 1.3 API, this module might 
>>> crash
>>> under EAPI! (please recompile it with -DEAPI)
>>>
>>> This is exactly the same warning that I get when I attempted to use 
>>> the
>>> binary module from the Jakarta site.  I have double checked that I am
>>> using my newly compiled module.  This is easy to do because my freshly
>>> compiled module is only 165852 while the binary module was 437664
>>> bytes.  So, why are these files so different in size; and, more
>>> importantly, how do I get rid of this warning?
>>>
>>> Below is the "Makedefs" file which was generated as part of my 
>>> building
>>> mod_webapp.so from source:
>>>
>>> Please help so that I can "Have fun..."
>>>
>>> Cynthia Jeness
>>>
>>> 
>-
>>>
>>>
>>>
>>> # @author  Pier Fumagalli 
>>> # @version $Id: Makedefs.in,v 1.11 2001/09/17 00:42:59 pier Exp $
>>>
>>> .SUFFIXES: .c .o
>>>
>>> #
>>> -
>>>
>>> # Programs discovered by "configure" during initialization
>>> #
>>> -
>>>
>>> TEST = /usr/bin/test
>>> TRUE = /bin/true
>>> ECHO = /bin/echo
>>> GREP = /bin/grep
>>> CAT = /bin/cat
>>> SED = /bin/sed
>>> LN = /bin/ln
>>> RM = /bin/rm
>>>
>>> #
>>> -
>>>
>>>  Compilation settings and Makefile macros
>>> #
>>> -
>>>
>>> # The target module to build
>>> MODULE = apache-1.3
>>> # The system which built this binary
>>> SYSTEM = linux-gnu-i686
>>> # Wether to build debug information or not
>>> DEBUG = false
>>> # The WebApp sources directory
>>> SRCDIR = /home/cj/tomcat/webapp-module-1.0-tc40
>>> # The compilation (this) directory
>>> TGTDIR = /home/cj/tomcat/webapp-module-1.0-tc40
>>> # The directory of a Tomcat 4.0 binary distribution
>>> TC4DIR =
>>> # The list of configure-generated files
>>> CFGFILES = ./Makefile ./Makedefs ./lib/Makefile ./java/Constants.java
>>> ./apache-1.3/Makefile ./config.cache
>>> ./config.log ./config.status
>>> # The file holding the list of makefile-generated files
>>> LSTFILE = $(TGTDIR)/config.list
>>> # GNU-Make style echo
>>> MECHO = $(ECHO) "$(MAKE)[$(MAKELEVEL)]:"
>>>

Re: mod_webapp -- EAPI error

[Cynthia Jeness]

John,

By searching through Google, I discovered this link to a slightly older set of  RPMS 
for
Tomcat including one for mod_webapp:

http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0/rpms/

This is not the link that you get from the Jakarta site.  The Jakarta link ends wiht
"4.0.1/rpms".

When I installed the 4.0/rpm version of mod_webapp, then my "EAPI" error went away and 
I
could load the "HelloWorldExample" servlet.  However, the changes that the RPM made to 
the
httpd.conf file seemed to be incorrect.  So I deleted these and added the lines 
specified
in the README.txt for mod_webapp.

I would still like to understand  how to compile from source and get an appropriate 
module
since it seems like the rpm for mod_webapp is not always provided.  Further, some of 
our
systems run Apache on Solaris where I need to be able to compile the source.

So, can anyone from the Apache team please help with this issue?

Cynthia


John Clayton wrote:

> I have just experienced the very same issue with the binary.  What's
> more, I can't even get configure to run while trying to build it from
> source, as it is reporting a syntax error on line 5.  Hmm 
>
> On Wednesday, December 26, 2001, at 10:45 AM, Cynthia Jeness wrote:
>
> > I got the sources for Apache 1.3.22, compiled and installed.
> >
> > Then I got the sources for mod_webapp.  After unpacking, I did the
> > following as described in the "README.txt" file:
> >
> > ./support/buildconf.sh
> > CFLAGS=-DEAPI \
> > ./configure --with-apxs=/usr/local/bin
> >
> > Then I executed make.  Watching the compiles display on my screen, the
> > "-DEAPI" flag was specified.
> >
> > The sources compiled and "mod_webapp.so" was created.  Then I copied
> > this module to my Apache modules directory,  modified the httpd.conf as
> > directed in the README.txt and started Apache.  Apache did start, but I
> > received the following warning:
> >
> > starting httpd: [Wed Dec 26 09:21:24 2001] [warn] Loaded DSO
> > modules/mod_webapp.so uses plain Apache 1.3 API, this module might crash
> > under EAPI! (please recompile it with -DEAPI)
> >
> > This is exactly the same warning that I get when I attempted to use the
> > binary module from the Jakarta site.  I have double checked that I am
> > using my newly compiled module.  This is easy to do because my freshly
> > compiled module is only 165852 while the binary module was 437664
> > bytes.  So, why are these files so different in size; and, more
> > importantly, how do I get rid of this warning?
> >
> > Below is the "Makedefs" file which was generated as part of my building
> > mod_webapp.so from source:
> >
> > Please help so that I can "Have fun..."
> >
> > Cynthia Jeness
> >
> > 
>-
> >
> >
> >
> > # @author  Pier Fumagalli 
> > # @version $Id: Makedefs.in,v 1.11 2001/09/17 00:42:59 pier Exp $
> >
> > .SUFFIXES: .c .o
> >
> > #
> > -
> >
> > # Programs discovered by "configure" during initialization
> > #
> > -
> >
> > TEST = /usr/bin/test
> > TRUE = /bin/true
> > ECHO = /bin/echo
> > GREP = /bin/grep
> > CAT = /bin/cat
> > SED = /bin/sed
> > LN = /bin/ln
> > RM = /bin/rm
> >
> > #
> > -
> >
> >  Compilation settings and Makefile macros
> > #
> > -
> >
> > # The target module to build
> > MODULE = apache-1.3
> > # The system which built this binary
> > SYSTEM = linux-gnu-i686
> > # Wether to build debug information or not
> > DEBUG = false
> > # The WebApp sources directory
> > SRCDIR = /home/cj/tomcat/webapp-module-1.0-tc40
> > # The compilation (this) directory
> > TGTDIR = /home/cj/tomcat/webapp-module-1.0-tc40
> > # The directory of a Tomcat 4.0 binary distribution
> > TC4DIR =
> > # The list of configure-generated files
> > CFGFILES = ./Makefile ./Makedefs ./lib/Makefile ./java/Constants.java
> > ./apache-1.3/Makefile ./config.cache
> > ./config.log ./config.status
> > # The file holding the list of makefile-generated files
> > LSTFILE = $(TGTDIR)/config.list
> > # GNU-Make style echo
> > MECHO = $(ECHO) "$(MAKE)[$(MAKELEVEL)]:"
> > #
> > -
> >
> > # APR library values
> > #
> > -
> >
> > # The APR source directory (if needed)
> > APR_SRCDIR = /home/cj/tomcat/webapp-module-1.0-tc40/apr
> > # Where libapr.a resides
> > APR_LIBDIR = /home/cj/tomcat/webapp-module-1.0-tc40/lib
> > # Where APR include files are located
> > APR_INCDIR = /home/cj/tomcat/webapp-module-1.0-tc40/apr/include
> > # Location of APRVARS
> > APR_VARFIL = /home/cj/tomcat/webapp-module-1.0-tc40/apr/APRVARS
>

Re: mod_webapp -- EAPI error

[John Clayton]

I have just experienced the very same issue with the binary.  What's 
more, I can't even get configure to run while trying to build it from 
source, as it is reporting a syntax error on line 5.  Hmm 




On Wednesday, December 26, 2001, at 10:45 AM, Cynthia Jeness wrote:

> I got the sources for Apache 1.3.22, compiled and installed.
>
> Then I got the sources for mod_webapp.  After unpacking, I did the
> following as described in the "README.txt" file:
>
> ./support/buildconf.sh
> CFLAGS=-DEAPI \
> ./configure --with-apxs=/usr/local/bin
>
> Then I executed make.  Watching the compiles display on my screen, the
> "-DEAPI" flag was specified.
>
> The sources compiled and "mod_webapp.so" was created.  Then I copied
> this module to my Apache modules directory,  modified the httpd.conf as
> directed in the README.txt and started Apache.  Apache did start, but I
> received the following warning:
>
> starting httpd: [Wed Dec 26 09:21:24 2001] [warn] Loaded DSO
> modules/mod_webapp.so uses plain Apache 1.3 API, this module might crash
> under EAPI! (please recompile it with -DEAPI)
>
> This is exactly the same warning that I get when I attempted to use the
> binary module from the Jakarta site.  I have double checked that I am
> using my newly compiled module.  This is easy to do because my freshly
> compiled module is only 165852 while the binary module was 437664
> bytes.  So, why are these files so different in size; and, more
> importantly, how do I get rid of this warning?
>
> Below is the "Makedefs" file which was generated as part of my building
> mod_webapp.so from source:
>
> Please help so that I can "Have fun..."
>
> Cynthia Jeness
>
> -
>
>
>
> # @author  Pier Fumagalli 
> # @version $Id: Makedefs.in,v 1.11 2001/09/17 00:42:59 pier Exp $
>
> .SUFFIXES: .c .o
>
> #
> -
>
> # Programs discovered by "configure" during initialization
> #
> -
>
> TEST = /usr/bin/test
> TRUE = /bin/true
> ECHO = /bin/echo
> GREP = /bin/grep
> CAT = /bin/cat
> SED = /bin/sed
> LN = /bin/ln
> RM = /bin/rm
>
> #
> -
>
>  Compilation settings and Makefile macros
> #
> -
>
> # The target module to build
> MODULE = apache-1.3
> # The system which built this binary
> SYSTEM = linux-gnu-i686
> # Wether to build debug information or not
> DEBUG = false
> # The WebApp sources directory
> SRCDIR = /home/cj/tomcat/webapp-module-1.0-tc40
> # The compilation (this) directory
> TGTDIR = /home/cj/tomcat/webapp-module-1.0-tc40
> # The directory of a Tomcat 4.0 binary distribution
> TC4DIR =
> # The list of configure-generated files
> CFGFILES = ./Makefile ./Makedefs ./lib/Makefile ./java/Constants.java
> ./apache-1.3/Makefile ./config.cache
> ./config.log ./config.status
> # The file holding the list of makefile-generated files
> LSTFILE = $(TGTDIR)/config.list
> # GNU-Make style echo
> MECHO = $(ECHO) "$(MAKE)[$(MAKELEVEL)]:"
> #
> -
>
> # APR library values
> #
> -
>
> # The APR source directory (if needed)
> APR_SRCDIR = /home/cj/tomcat/webapp-module-1.0-tc40/apr
> # Where libapr.a resides
> APR_LIBDIR = /home/cj/tomcat/webapp-module-1.0-tc40/lib
> # Where APR include files are located
> APR_INCDIR = /home/cj/tomcat/webapp-module-1.0-tc40/apr/include
> # Location of APRVARS
> APR_VARFIL = /home/cj/tomcat/webapp-module-1.0-tc40/apr/APRVARS
> # Extra APR C compilation flags
> APR_CFLAGS =
> # Extra APR C macro pre-processor flags
> APR_CPPFLAGS = -DLINUX=2 -D_REENTRANT
> # Extra APR inclusion flags
> APR_INCLUDES =
> # Extra APR linker flags
> APR_LDFLAGS =
> # Extra APR libraries required for linking
> APR_LIBS = -lm -lcrypt -lnsl -ldl
> #
> -
>
> # C Compiler settings
> #
> -
>
> # Library archiver
> AR = /usr/bin/ar
> # C compiler
> CC = /usr/bin/gcc
> # C macro pre-processor
> CPP = /usr/bin/gcc -E
> # Library updater
> RANLIB = /usr/bin/ranlib
> # C compilation flags
> CFLAGS = -DEAPI
> # C macro pre-processor flags
> CPPFLAGS =
>
> #
> -
>
> # Java Compiler settings
> #
> -
>
> # The JVM home directory
> JAVA_HOME =
> # Jar archiver
> JAR =
> # Java compiler
> JAVAC =
> # JavaDoc documentation tool
> JAVADOC =
> # Java compilation flags
> JAVACFLAGS =
> # Java Class Path
> CLASSPATH =
>
> #
> -

mod_webapp -- EAPI error

[Cynthia Jeness]

I got the sources for Apache 1.3.22, compiled and installed.

Then I got the sources for mod_webapp.  After unpacking, I did the
following as described in the "README.txt" file:

./support/buildconf.sh
CFLAGS=-DEAPI \
./configure --with-apxs=/usr/local/bin

Then I executed make.  Watching the compiles display on my screen, the
"-DEAPI" flag was specified.

The sources compiled and "mod_webapp.so" was created.  Then I copied
this module to my Apache modules directory,  modified the httpd.conf as
directed in the README.txt and started Apache.  Apache did start, but I
received the following warning:

starting httpd: [Wed Dec 26 09:21:24 2001] [warn] Loaded DSO
modules/mod_webapp.so uses plain Apache 1.3 API, this module might crash
under EAPI! (please recompile it with -DEAPI)

This is exactly the same warning that I get when I attempted to use the
binary module from the Jakarta site.  I have double checked that I am
using my newly compiled module.  This is easy to do because my freshly
compiled module is only 165852 while the binary module was 437664
bytes.  So, why are these files so different in size; and, more
importantly, how do I get rid of this warning?

Below is the "Makedefs" file which was generated as part of my building
mod_webapp.so from source:

Please help so that I can "Have fun..."

Cynthia Jeness

-



# @author  Pier Fumagalli 
# @version $Id: Makedefs.in,v 1.11 2001/09/17 00:42:59 pier Exp $

.SUFFIXES: .c .o

#
-

# Programs discovered by "configure" during initialization
#
-

TEST = /usr/bin/test
TRUE = /bin/true
ECHO = /bin/echo
GREP = /bin/grep
CAT = /bin/cat
SED = /bin/sed
LN = /bin/ln
RM = /bin/rm

#
-

 Compilation settings and Makefile macros
#
-

# The target module to build
MODULE = apache-1.3
# The system which built this binary
SYSTEM = linux-gnu-i686
# Wether to build debug information or not
DEBUG = false
# The WebApp sources directory
SRCDIR = /home/cj/tomcat/webapp-module-1.0-tc40
# The compilation (this) directory
TGTDIR = /home/cj/tomcat/webapp-module-1.0-tc40
# The directory of a Tomcat 4.0 binary distribution
TC4DIR =
# The list of configure-generated files
CFGFILES = ./Makefile ./Makedefs ./lib/Makefile ./java/Constants.java
./apache-1.3/Makefile ./config.cache
./config.log ./config.status
# The file holding the list of makefile-generated files
LSTFILE = $(TGTDIR)/config.list
# GNU-Make style echo
MECHO = $(ECHO) "$(MAKE)[$(MAKELEVEL)]:"
#
-

# APR library values
#
-

# The APR source directory (if needed)
APR_SRCDIR = /home/cj/tomcat/webapp-module-1.0-tc40/apr
# Where libapr.a resides
APR_LIBDIR = /home/cj/tomcat/webapp-module-1.0-tc40/lib
# Where APR include files are located
APR_INCDIR = /home/cj/tomcat/webapp-module-1.0-tc40/apr/include
# Location of APRVARS
APR_VARFIL = /home/cj/tomcat/webapp-module-1.0-tc40/apr/APRVARS
# Extra APR C compilation flags
APR_CFLAGS =
# Extra APR C macro pre-processor flags
APR_CPPFLAGS = -DLINUX=2 -D_REENTRANT
# Extra APR inclusion flags
APR_INCLUDES =
# Extra APR linker flags
APR_LDFLAGS =
# Extra APR libraries required for linking
APR_LIBS = -lm -lcrypt -lnsl -ldl
#
-

# C Compiler settings
#
-

# Library archiver
AR = /usr/bin/ar
# C compiler
CC = /usr/bin/gcc
# C macro pre-processor
CPP = /usr/bin/gcc -E
# Library updater
RANLIB = /usr/bin/ranlib
# C compilation flags
CFLAGS = -DEAPI
# C macro pre-processor flags
CPPFLAGS =

#
-

# Java Compiler settings
#
-

# The JVM home directory
JAVA_HOME =
# Jar archiver
JAR =
# Java compiler
JAVAC =
# JavaDoc documentation tool
JAVADOC =
# Java compilation flags
JAVACFLAGS =
# Java Class Path
CLASSPATH =

#
-

# ScanDoc Documentation tool settings
#
-

# PERL interpreter
PERL =
# ScanDoc documentation tool
SCANDOC =
# Scandoc flags
SCANDOCFLAGS =

#
-

# C-Compilation default setting
#
-

ALL_CFLAGS = $(CFLAGS) $(CPPFLAGS) \
$(APR_CFLAGS) $(APR_CPPFLAGS) $(APR_INCLUDES) \
-I$(