tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 29911] New: - build fails with "unable to infer tagged configuration"
Date Sun, 04 Jul 2004 16:55:02 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=29911>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=29911

build fails with "unable to infer tagged configuration"

           Summary: build fails with "unable to infer tagged configuration"
           Product: Tomcat 4
           Version: Unknown
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Critical
          Priority: Other
         Component: Connector:Coyote JK 2
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: zrockenbaugh@yahoo.com


Downloading the latest connector source, I did the following:

tar xzf jakarta-tomcat-connectors-4.1.30-src.tar.gz
cp build.properties.jk jakarta-tomcat-connectors-4.1.30-src/jk/build.properties
cd jakarta-tomcat-connectors-4.1.30-src/jk/native2
ant jkant
ant

The build.properties.jk file defines tomcat40.home, apache2.home and comments
out all other Tomcat versions and web servers.

When I run this, I get the following:

Buildfile: build.xml

jkant:

jkant:

BUILD SUCCESSFUL
Total time: 1 second
Buildfile: build.xml

init.taskdef:

guess.os:
     [echo] build.properties i386.Linux
     [echo] Linux:true Win32:${win32} Netware:${netware} Solaris:${solaris}
HPUX:${hpux}

init.win32.properties:

init.win32.mc:

init.win32:

init.netware:

init.os:

guess.server:
     [echo] Apache2 /usr/local/apache2 true
     [echo] Apache13 /usr ${apache13.detect}
     [echo] IIS ${iis.home} ${iis.detect}
     [echo] Iplanet ${iplanet.home} ${iplanet.detect}
     [echo] AOLserver ${aolserver.home} ${aolserver.detect}
     [echo] JNI true


init:

apache20:
       [so] Compiling 42 out of 42
Compiling
/fast/development/new_main/thirdparty/httpd/jakarta-tomcat-connectors-4.1.30-src/jk/native2/common/jk_channel.c
       [so] Compile failed 1
/fast/development/new_main/thirdparty/httpd/jakarta-tomcat-connectors-4.1.30-src/jk/native2/common/jk_channel.c
       [so] Command:libtool --mode=compile cc -c -o
/fast/development/new_main/thirdparty/httpd/jakarta-tomcat-connectors-4.1.30-src/jk/build/jk2/apache2/common/jk_channel.o
-I/fast/development/new_main/thirdparty/httpd/jakarta-tomcat-connectors-4.1.30-src/jk/native2/common
-I/usr/local/apache2/include -I/usr/local/apache2/include
-I/usr/local/apache2/include
-I/fast/development/new_main/thirdparty/httpd/jakarta-tomcat-connectors-4.1.30-src/jk/native2/include
-I/fast/development/new_main/build/lib/java/jre/../include
-I/fast/development/new_main/build/lib/java/jre/../include/linux -W -D_REENTRANT
-DCHUNK_SIZE=4096 -DUSE_APACHE_MD5 -DHAS_APR -DHAVE_JNI
/fast/development/new_main/thirdparty/httpd/jakarta-tomcat-connectors-4.1.30-src/jk/native2/common/jk_channel.c
       [so] Output:
       [so] libtool: compile: unable to infer tagged configuration
       [so] StdErr:
       [so] libtool: compile: specify a tag with `--tag'


(The jkant target was built from a previous run.)

By copying the command and adding "--tag=cc" or "--tag=gcc" to the begining of
the libtool options, I was able to get it to run without errors. I'm educating
myself on the 'so' task to see if I can get the build.xml file to run for me.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message