public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Alexandre Petit-Bianco <apbianco@cygnus.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: java/4360: libjava fails to compile on i686-pc-linux-gnu (AttributedString) Date: Wed, 19 Sep 2001 08:26:00 -0000 [thread overview] Message-ID: <20010919152601.12941.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR java/4360; it has been noted by GNATS. From: Alexandre Petit-Bianco <apbianco@cygnus.com> To: georg.wild@gmx.de Cc: gcc-gnats@gcc.gnu.org Subject: Re: java/4360: libjava fails to compile on i686-pc-linux-gnu (AttributedString) Date: Wed, 19 Sep 2001 08:18:45 -0700 (PDT) georg.wild@gmx.de writes: > I often install the latest version of the cvs snapshot. Since a few > (I think months) libjava fails to build. Hmm. I can assure you that a lot of people are successfully building libjava on linux/x86 every days. For instance, I think that this week snapshot ought to work. > .... > gcj -B/root/gcc/libjava/ --encoding=UTF-8 -C -g -classpath /root/gcc/libjava:. -d /root/gcc/libjava java/text/AttributedString.java > /root/gcc/libjava/java/text/AttributedString.java:45: Class `java.text.AttributedString' already defined in java/text/AttributedString.java:45. > public class AttributedString > ^ Could you try the patch I posted to java/2791? It seems that you're building libjava as root. I don't see why it would fail, but I never tried that configuration. ./A
next reply other threads:[~2001-09-19 8:26 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-09-19 8:26 Alexandre Petit-Bianco [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-09-22 11:52 apbianco 2001-09-22 11:26 Alexandre Petit-Bianco 2001-09-22 9:26 Alexandre Petit-Bianco 2001-09-22 3:46 Georg Wild 2001-09-22 3:26 Georg Wild 2001-09-21 15:46 Alexandre Petit-Bianco 2001-09-21 13:06 Alexandre Petit-Bianco 2001-09-21 11:26 Alexandre Petit-Bianco 2001-09-20 8:16 Alexandre Petit-Bianco 2001-09-19 6:06 georg.wild
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20010919152601.12941.qmail@sourceware.cygnus.com \ --to=apbianco@cygnus.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).