This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Installing libjava fails
- From: Andreas Schwab <schwab at suse dot de>
- To: Alexandre Oliva <aoliva at redhat dot com>
- Cc: gcc at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org, java at gcc dot gnu dot org
- Date: Thu, 28 Feb 2002 10:39:32 +0100
- Subject: Re: Installing libjava fails
- References: <jeofieww2h.fsf@sykes.suse.de> <jelmdgrr1x.fsf@sykes.suse.de><orit8icp3k.fsf@free.redhat.lsd.ic.unicamp.br>
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."