Installing libjava fails

Installing libjava fails

[Andreas Schwab]

Installing libjava fails in current snapshot:

make[3]: Entering directory `/usr/src/packages/BUILD/gcc-3.1-20020223/obj-i486-suse-linux/i486-suse-linux/libjava'
/bin/sh ./libtool  --mode=install /bin/sh /usr/src/packages/BUILD/gcc-3.1-20020223/install-sh -c libgcj.la /usr/lib/libgcj.la
libtool: install: warning: relinking `libgcj.la'
cd /usr/src/packages/BUILD/gcc-3.1-20020223/obj-i486-suse-linux/i486-suse-linux/libjava; /bin/sh ./libtool --mode=relink /usr/src/packages/BUILD/gcc-3.1-20020223/obj-i486-suse-linux/gcc/xgcc -shared-libgcc -B/usr/src/packages/BUILD/gcc-3.1-20020223/obj-i486-suse-linux/gcc/ -nostdinc++ -nostdinc++ -I/usr/src/packages/BUILD/gcc-3.1-20020223/obj-i486-suse-linux/i486-suse-linux/libstdc++-v3/include/i486-suse-linux -I/usr/src/packages/BUILD/gcc-3.1-20020223/obj-i486-suse-linux/i486-suse-linux/libstdc++-v3/include -I/usr/src/packages/BUILD/gcc-3.1-20020223/libstdc++-v3/libsupc++ -I/usr/src/packages/BUILD/gcc-3.1-20020223/libstdc++-v3/libio -I/usr/src/packages/BUILD/gcc-3.1-20020223/libstdc++-v3/include/backward -I/usr/src/packages/BUILD/gcc-3.1-20020223/libstdc++-v3/testsuite -L/usr/src/packages/BUILD/gcc-3.1-20020223/obj-i486-suse-linux/i486-suse-linux/libstdc++-v3/src -L/usr/src/packages/BUILD/gcc-3.1-20020223/obj-i486-suse-linux/i486-suse-linux/libstdc++-v3/src/.libs -B/usr/i486-suse-linux/bin/ -B/usr/i486-suse-linux/lib/ -isystem /usr/i486-suse-linux/include -L/usr/src/packages/BUILD/gcc-3.1-20020223/obj-i486-suse-linux/i486-suse-linux/libjava -ffloat-store -g -O2 -o libgcj.la -objectlist libgcj.objectlist ../libffi/libfficonvenience.la -rpath /usr/lib -rpath /usr/lib -lpthread ./libltdl/libltdlc.la ./../boehm-gc/libgcjgc.la -L/usr/src/packages/BUILD/gcc-3.1-20020223/obj-i486-suse-linux/i486-suse-linux/libjava/../boehm-gc/.libs -lz -version-info 2:0:0
libtool: link: unable to infer tagged configuration
libtool: link: specify a tag with `--tag'
libtool: install: error: relink `libgcj.la' with the above command before installing it

The libtool configuration has the following value for CC with tag CXX:

# A language-specific compiler.
CC="/usr/src/packages/BUILD/gcc-3.1-20020223/obj-i486-suse-linux/gcc/xgcc -shared-libgcc -B/usr/src/packages/BUILD/gcc-3.1-20020223/obj-i486-suse-linux/gcc/ -nostdinc++  -L/usr/src/packages/BUILD/gcc-3.1-20020223/obj-i486-suse-linux/i486-suse-linux/libstdc++-v3/src -L/usr/src/packages/BUILD/gcc-3.1-20020223/obj-i486-suse-linux/i486-suse-linux/libstdc++-v3/src/.libs -B/usr/i486-suse-linux/bin/ -B/usr/i486-suse-linux/lib/ -isystem /usr/i486-suse-linux/include"

The difference is that

-nostdinc++ -I/usr/src/packages/BUILD/gcc-3.1-20020223/obj-i486-suse-linux/i486-suse-linux/libstdc++-v3/include/i486-suse-linux -I/usr/src/packages/BUILD/gcc-3.1-20020223/obj-i486-suse-linux/i486-suse-linux/libstdc++-v3/include -I/usr/src/packages/BUILD/gcc-3.1-20020223/libstdc++-v3/libsupc++ -I/usr/src/packages/BUILD/gcc-3.1-20020223/libstdc++-v3/libio -I/usr/src/packages/BUILD/gcc-3.1-20020223/libstdc++-v3/include/backward -I/usr/src/packages/BUILD/gcc-3.1-20020223/libstdc++-v3/testsuite

has been inserted into the relink command.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE GmbH, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: Installing libjava fails

[Andreas Schwab]

|> Installing libjava fails in current snapshot:

Here is a patch:

2002-02-26  Andreas Schwab  <schwab@suse.de>

	* acinclude.m4 (LIB_AC_PROG_CXX): Use glibjava_CXX instead of
	glibcpp_CXX, since libjava uses even another CXX.
        * aclocal.m4, configure: Regenerated.

Index: libjava/acinclude.m4
===================================================================
RCS file: /cvs/gcc/gcc/libjava/acinclude.m4,v
retrieving revision 1.18
diff -u -a -r1.18 libjava/acinclude.m4
--- libjava/acinclude.m4	2002/02/22 21:31:05	1.18
+++ libjava/acinclude.m4	2002/02/26 15:53:53
@@ -81,23 +81,23 @@
 
 AC_PROG_CC
 
-# We use the libstdc++-v3 version of LIB_AC_PROG_CXX, that gets
-# glibcpp_CXX cached instead of CXX.  That's because we're passed a
+# We use the libstdc++-v3 version of LIB_AC_PROG_CXX, but use
+# glibjava_CXX instead of glibcpp_CXX.  That's because we're passed a
 # different definition of CXX than other directories, since we don't
 # depend on libstdc++-v3 having already been built.
 AC_DEFUN(LIB_AC_PROG_CXX,
 [AC_BEFORE([$0], [AC_PROG_CXXCPP])dnl
 dnl Fool anybody using AC_PROG_CXX.
 AC_PROVIDE([AC_PROG_CXX])
-# Use glibcpp_CXX so that we do not cause CXX to be cached with the
-# flags that come in CXX while configuring libstdc++.  They're different
+# Use glibjava_CXX so that we do not cause CXX to be cached with the
+# flags that come in CXX while configuring libjava.  They're different
 # from those used for all other target libraries.  If CXX is set in
 # the environment, respect that here.
-glibcpp_CXX=$CXX
-AC_CHECK_PROGS(glibcpp_CXX, $CCC c++ g++ gcc CC cxx cc++, gcc)
+glibjava_CXX=$CXX
+AC_CHECK_PROGS(glibjava_CXX, $CCC c++ g++ gcc CC cxx cc++, gcc)
 AC_SUBST(CXX)
-CXX=$glibcpp_CXX
-test -z "$glibcpp_CXX" && AC_MSG_ERROR([no acceptable c++ found in \$PATH])
+CXX=$glibjava_CXX
+test -z "$glibjava_CXX" && AC_MSG_ERROR([no acceptable c++ found in \$PATH])
 
 AC_PROG_CXX_GNU
 

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE GmbH, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: Installing libjava fails

[Alexandre Oliva]

On Feb 26, 2002, Andreas Schwab <schwab@suse.de> wrote:

> |> Installing libjava fails in current snapshot:

> Here is a patch:

> 2002-02-26  Andreas Schwab  <schwab@suse.de>

> 	* acinclude.m4 (LIB_AC_PROG_CXX): Use glibjava_CXX instead of
> 	glibcpp_CXX, since libjava uses even another CXX.
>         * aclocal.m4, configure: Regenerated.

Oh!  I see...  I had missed the variations caused by libstdc++-v3.
Anyway, I don't think there's any point in passing libstdc++-v3 flags
to libjava.  libjava doesn't depend on libstdc++-v3 at all, AFAIK.  So
we might as well adjust libstdcxx_flags such that it is empty for
libjava too, instead of using or patch.  Comments?

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist                Professional serial bug killer

Re: Installing libjava fails

[Andreas Schwab]

Alexandre Oliva <aoliva@redhat.com> writes:

|> On Feb 26, 2002, Andreas Schwab <schwab@suse.de> wrote:
|> 
|> > |> Installing libjava fails in current snapshot:
|> 
|> > Here is a patch:
|> 
|> > 2002-02-26  Andreas Schwab  <schwab@suse.de>
|> 
|> > 	* acinclude.m4 (LIB_AC_PROG_CXX): Use glibjava_CXX instead of
|> > 	glibcpp_CXX, since libjava uses even another CXX.
|> >         * aclocal.m4, configure: Regenerated.
|> 
|> Oh!  I see...  I had missed the variations caused by libstdc++-v3.
|> Anyway, I don't think there's any point in passing libstdc++-v3 flags
|> to libjava.  libjava doesn't depend on libstdc++-v3 at all, AFAIK.  So
|> we might as well adjust libstdcxx_flags such that it is empty for
|> libjava too, instead of using or patch.  Comments?

I'm currently testing the appendend patch, but I don't think that the
above changes do any harm, and could be left in regardless.

Andreas.

2002-02-28  Andreas Schwab  <schwab@suse.de>

	* configure.in (libstdcxx_flags): Don't use libstdc++-v3's flags
	for libjava.

--- configure.in.~1.119.~	Sun Feb 24 15:45:59 2002
+++ configure.in	Thu Feb 28 10:29:18 2002
@@ -49,8 +49,8 @@
 fi
 
 libstdcxx_version="target-libstdc++-v3"
-# Don't use libstdc++-v3's flags to configure/build itself.
-libstdcxx_flags='`case $$dir in libstdc++-v3) ;; *) test ! -f $$r/$(TARGET_SUBDIR)/libstdc++-v3/testsuite_flags || $(SHELL) $$r/$(TARGET_SUBDIR)/libstdc++-v3/testsuite_flags --build-includes;; esac` -L$$r/$(TARGET_SUBDIR)/libstdc++-v3/src -L$$r/$(TARGET_SUBDIR)/libstdc++-v3/src/.libs'
+# Don't use libstdc++-v3's flags to configure/build itself or libjava.
+libstdcxx_flags='`case $$dir in libstdc++-v3 | libjava) ;; *) test ! -f $$r/$(TARGET_SUBDIR)/libstdc++-v3/testsuite_flags || $(SHELL) $$r/$(TARGET_SUBDIR)/libstdc++-v3/testsuite_flags --build-includes;; esac` -L$$r/$(TARGET_SUBDIR)/libstdc++-v3/src -L$$r/$(TARGET_SUBDIR)/libstdc++-v3/src/.libs'
 
 # these tools are built for the host environment
 # Note, the powerpc-eabi build depends on sim occurring before gdb in order to

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE GmbH, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: Installing libjava fails

[Alexandre Oliva]

On Feb 28, 2002, Andreas Schwab <schwab@suse.de> wrote:

> I'm currently testing the appendend patch, but I don't think that the
> above changes do any harm, and could be left in regardless.

Don't bother.  I forgot to mention that I included this change in the
patch I wrote to revamp -shared-libgcc last night.

Sorry,

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist                Professional serial bug killer