File: README.build

package info (click to toggle)
jserv 1.1.2-2
  • links: PTS
  • area: contrib
  • in suites: woody
  • size: 4,584 kB
  • ctags: 3,019
  • sloc: sh: 7,715; java: 6,635; ansic: 5,013; makefile: 814; perl: 39; xml: 32
file content (71 lines) | stat: -rw-r--r-- 3,044 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
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 the links provided 
below.

-------------
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.

To install libtool properly, you need to install it on top of your automake 
installation. If you get errors when running aclocal (ie: macro 
`AM_PROG_LIBTOOL' not found in library), it is because you didn't install 
libtool properly.

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 java-apache@ developer mailing list.