All changes to project files are done via version control (svn) and get
automatically send out to the dev list. Any tomcat-dev archive contains
the messages.
This one for instance can be found at:
http://marc.info/?l=tomcat-dev&m=117908298415733&w=2
The only file which changed was configure.i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rainer,
Rainer Jung wrote:
> Hi Christopher,
>
> I've now reordered configure and added a warning at the end, in case
> CC doesn't really fit, to what apxs spits out.
Excellent!
> You might want to test the new configure script. For convenience you
Hi Christopher,
Perhaps this (potential - I've /never/ seen it on other systems) issue
could be avoided by adding a bit of documentation to the BUILD.txt file
that says "if you get a weird error about tags not being defined, try
running this:
export CC=`apxs -q CC`
I've now reordered configur
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rainer,
Thanks for the explanations of everything. I'm still certainly not ready
to become an autoconf master, but...
Rainer Jung wrote:
> In case we build an Apache httpd 2.x module, we are using the httpd
> provided instance of libtool for maximum
Okay, I tried this:
$ export CC=i486-linux-gnu-gcc
$ make clean
$ ./configure --with-apxs=/usr/bin/apxs2
$ make
Looks like it works this way. Weird. Why should the name of the compiler
matter?
The TODO file of libtool says:
* ... This includes writing libtool not to be so dependent on the
co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
How does CC get picked when configure runs? I tried reading the
configure script but got lost pretty quickly.
It looks like apxs knows what CC should be set to, though:
$ apxs2 -q CC
i486-linux-gnu-gcc
Does it make sense for configure to use a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rainer,
Rainer Jung wrote:
> that means the guys who built APR (and most likely httpd) for Debian
> used i486-linux-gnu-gcc and not gcc as their compiler. Those might be
> the same (symlinks or so), but libtool remembers the compilatrion
> environment
Hi Christopher,
that means the guys who built APR (and most likely httpd) for Debian
used i486-linux-gnu-gcc and not gcc as their compiler. Those might be
the same (symlinks or so), but libtool remembers the compilatrion
environment it was created in and refuses to work in another one.
If
w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mladen,
Mladen Turk wrote:
> Christopher Schultz wrote:
>
>> libtool: compile: unable to infer tagged configuration
>> libtool: compile: specify a tag with `--tag'
>> make[1]: *** [jk_ajp12_worker.lo] Error 1
>> make[1]: Leaving directory
>> `/usr/lo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rainer,
Thanks for the quick response. I took another look at the configure
output and it appears that workaround I found was valid. I (blindly)
followed the instructions and was able to build a binary.
Rainer Jung wrote:
> this usually happens, if t
Christopher Schultz wrote:
libtool: compile: unable to infer tagged configuration
libtool: compile: specify a tag with `--tag'
make[1]: *** [jk_ajp12_worker.lo] Error 1
make[1]: Leaving directory
`/usr/local/src/tomcat-connectors-1.2.22-src/native/common'
make: *** [all-recursive] Error 1
Can
Hi Christopher,
this usually happens, if the value of the CC environment variable during
the creation of libtool differs from the one used when you are using
libtool.
For example: one might use CC="gcc -specs=/my/own/specs/file" when
libtool gets created and later use CC=gcc during mod_jk co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
I finally beat my Debian installation into submission so it would
install "apxs" so I could build mod_jk for my package-managed apache2
(have been running from source for a lng time).
Right out of the box, mod_jk won't build:
$ wget
'http:/
13 matches
Mail list logo
