Failed to build libgcj / proplem with libtool
Alexandre Oliva
aoliva@redhat.com
Mon Sep 11 23:50:00 GMT 2000
On Sep 12, 2000, Alexandre Oliva <aoliva@redhat.com> wrote:
> On Sep 11, 2000, Bryce McKinlay <bryce@albatross.co.nz> wrote:
>> Michael Scheuner wrote:
>>> Hi,
>>>
>>> when trying to build the latest CVS-libgci (2000/09/10), make exits with the
>>> following:
>>>
>>> make[2]: Entering directory `/usr/src/libgcj-build/i686-pc-linux-gnu/libjava'
>>> /bin/sh ./libtool --mode=compile gcj -fassume-compiled
>>> -fclasspath=/usr/src/libgcj-build/i686-pc-linux-gnu/libjava
>>> -L/usr/src/libgcj-build/i686-pc-linux-gnu/libjava -g -ffloat-store -c -o
>>> gnu/gcj/convert/BytesToUnicode.lo
>>> ../../../libgcj/libjava/gnu/gcj/convert/BytesToUnicode.java
>>> libtool: compile: unable to infer tagged configuration
>>> libtool: compile: specify a tag with `--tag'
>> I got this too. It looks like there might be a problem with the new
>> multi-language libtool that was installed today.
> Remove config.cache from the target directory and get config.status to
> be re-run in the libjava directory. The problem should go away.
Scratch that. The problem was caused by one of those last-minute
changes that shouldn't cause any problem, but do :-(
I used to use AM_PROG_GCJ in libjava/configure.in, and libtool.m4
correctly detected its use and triggered the rule to add a gcj
configuration to libtool. However, in the last minute, I switched to
LT_AC_PROG_GCJ, that is an (almost) equivalent libtool macro, but it
turned out that it wasn't auto-detected :-(
Here's a patch that fixes this problem. I'm checking it in along with
an updated libjava/configure.
Sorry about the trouble, once again :-(
More information about the Java-patches
mailing list