----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
Sorry, maybe I'm being dense, but I did read the README.build
document, (before I made the original post.) Attached (at the end of
this email) is the README.build that I have checked out of CVS. Is
there a more recent one, maybe that's not checked in yet?
The README says: get autoconf and automake, run aclocal, autoconf and
automake, and if they produce any output (which they do), consult the
mailing list.
My environment is Solaris 2.7, autoconf-2.13, automake-1.4, checked
out JServ from CVS 31-jan-2000 3:00PM EST. Here's the output:
# aclocal
aclocal: configure.in: 39: macro `AM_DISABLE_STATIC' not found in library
aclocal: configure.in: 40: macro `AM_PROG_LIBTOOL' not found in library
# autoconf
autoconf: Undefined macros:
configure.in:395:AC_PROG_JAVATOOL(JAVA,java,[ Java runtime])
configure.in:396:AC_PROG_JAVATOOL(JAVAC,javac,[ Java compiler])
configure.in:397:AC_PROG_JAVATOOL(JAVADOC,javadoc,[ Java documentation compiler],
configure.in:399:AC_PROG_JAVATOOL(JAR,jar,[ Java Archiver])
configure.in:401:AC_PATH_JAVACLASS(JSDK,JSDK2.0,javax.servlet.Servlet,[ Where to
find the JSDK 2.0 classes])
configure.in:404:AC_PATH_EXTRA(JSDK)
configure.in:452:AC_PROG_JAVATOOL(JARSIGNER,jarsigner,[JAR file signer])
# automake
#
Thanks,
-billo
From: jon * <[EMAIL PROTECTED]>
Date: Mon, 31 Jan 2000 11:58:23 -0800
on 1/31/00 11:40 AM, Ryan Vanderwerf <[EMAIL PROTECTED]> wrote:
> I'm getting some config errors with the latest cvs of jserv:
> 13:36 $ autoconf configure.in >configure
Oh come on, I just posted about something like this about 2 hours ago...
read the jserv/README.build document.
-jon
-------------------------------------
README.build:
This file contains an overview of the autoconf/automake/libtool tandem
used to build Apache JServ on unix type platforms.
First a quick overview of the tools used (don't go get 'em yet you
probably won't need 'em). They can be downloaded from any GNU mirror.
-------------
autoconf-2.13 <http://sourceware.cygnus.com/autoconf/>
autoconf is a macro package (uses m4, and you'll probably want to get
the GNU version). autoconf takes a configure.in file and substitutes
all the macros for the corresponding shell code and generates the
configure script. You don't need to get autoconf unless you are
planning on experimenting with the configure.in file.
Most macros used come with autoconf but any macros in the aclocal.m4
file are also included. Don't edit this file though, it is generated
with aclocal which is a tool that comes with automake and is described
further below.
When the configure script is run it just executes all the shell code
for the macros in configure.in. This usually includes checking for
programs (like gcc and javac), headers (like the Apache headers), and
other stuff. Then it uses this information to generate a list of sed
replacements and stores them in config.status. These sed replacements
are executed in the files that occur in the AC_OUTPUT macro that
usually occurs at the end of the configure.in file. You can
regenerate these files at any time by just running config.status.
However if you change the configure.in file you have to re-run
autoconf before those changes will take place.
-------------
automake-1.4 <http://sourceware.cygnus.com/automake/>
automake is a tool for generating the Makefile.in files that configure
processes into Makefiles. It makes creating Makefiles really easy as
can be seen by looking at the Makefile.am files. These files tend are
meant to encompass the functionality of your typical GNU makefile
setup including installation and distribution needs.
automake 1.3b may also work, but other versions of 1.3 will not.
-----------
libtool-1.3.3 <http://www.gnu.org/software/libtool/libtool.html>
libtool is a script that knows how to build libraries (shared and
static) on almost every platform in existence. You'll never have to
touch this tool, it is generated by configure. You don't even have to
download it, all the necessary files are in the config dir.
>From the webpage for libtool:
NOTE: The vendor-distributed HP-UX sed(1) and make(1) programs are
horribly broken, and cannot handle libtool's requirements, so users may
report unusual problems. There is no workaround except to install a
working sed (such as GNU sed) and make (such as GNU make) on these systems.
-----------
Now, to use these tools, run the following:
# aclocal
# autoconf
# automake
There shouldn't be any output to these commands -- if there is, make sure
you have the versions specified above, and if the problems persist, contact
the developer mailing list.
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]