tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rainer Jung <rainer.j...@kippdata.de>
Subject Re: [mod_jk] 1.2.22 won't build (libtool error) :(
Date Fri, 11 May 2007 19:53:34 GMT
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

which i486-linux-gnu-gcc

produces a result, i.e. there is a binary i486-linux-gnu-gcc in your 
binary search path, you should be able to build httpd modules with the 
apr libtool by specifying

export CC=i486-linux-gnu-gcc

before running configure.

If i486-linux-gnu-gcc is not in your PATH, you might still find it in 
some dirctory you simply need to add to your PATH.

Google suggests, that it is

usr/bin/i486-linux-gnu-gcc in package devel/gcc

And from

http://buildd.debian.org/fetch.cgi?pkg=apr;ver=1.2.7-8.2;arch=i386;stamp=1166604063

we can guess, that in fact debian builds apr with gcc renamed to 
i486-linux-gnu-gcc.

So the *correct* solution should be:

export CC=i486-linux-gnu-gcc
configure ..
make

Regards,

Rainer


Christopher Schultz wrote:
> -----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 the value of the CC environment variable during
>> the creation of libtool differs from the one used when you are using
>> libtool.
> 
> I'm using binary packages directly from Debian. It looks like libtool
> comes from the "libapr1-dev" packages, I have no idea how it was created. :(
> 
>> If I check for the CC settings in my libtool it says:
> 
> Okay, mine says:
> 
> LTCC="i486-linux-gnu-gcc"
> CC="i486-linux-gnu-gcc"
> LTCC="i486-linux-gnu-gcc"
> CC="i486-linux-gnu-g++"
> 
> I made your suggested changes to libtool and here's the output of make, now:
> 
> $ make clean
> $ ./configure --with-apxs=/usr/bin/apxs2
> $ make
> 
> Making all in common
> make[1]: Entering directory
> `/usr/local/src/tomcat-connectors-1.2.22-src/native/common'
> /usr/share/apr-1.0/build/libtool --silent --mode=compile gcc
> - -I/usr/include/apache2 -g -O2 -D_GNU_SOURCE -D_LARGEFILE64_SOURCE
> - -DLINUX=2 -D_REENTRANT -I/usr/include/apr-1.0 -I/usr/include/openssl
> - -I/usr/include/postgresql -I/usr/include/xmltok -pthread   -DHAVE_APR
> - -I/usr/include/apr-1.0 -I/usr/include/apr-1.0 -g -O2  -I /include -I
> /include/ -c jk_ajp12_worker.c -o jk_ajp12_worker.lo
> Calling func_infer_tag  gcc -I/usr/include/apache2 -g -O2 -D_GNU_SOURCE
> - -D_LARGEFILE64_SOURCE -DLINUX=2 -D_REENTRANT -I/usr/include/apr-1.0
> - -I/usr/include/openssl -I/usr/include/postgresql -I/usr/include/xmltok
> - -pthread -DHAVE_APR -I/usr/include/apr-1.0 -I/usr/include/apr-1.0 -g -O2
> - -I /include -I /include/ -c
> Starting func_infer_tag...
> available_tags:  CXX
> tagname:
> Checking against:  i486-linux-gnu-gcc * | i486-linux-gnu-gcc * |
> i486-linux-gnu-gcc * | i486-linux-gnu-gcc * |   i486-linux-gnu-gcc* |
> i486-linux-gnu-gcc * |  i486-linux-gnu-gcc * | i486-linux-gnu-gcc *)
> 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
> 
> Oddly enough, it looks like it already recognizes the "CXX" tag as being
> available. Note that I have no idea what I'm talking about at all ;)
> 
> - -chris

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message