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: Fri, 21 Sep 2001 15:46:00 -0000	[thread overview]
Message-ID: <20010921224601.28245.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" <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: Fri, 21 Sep 2001 15:42:38 -0700 (PDT)

 Georg Wild writes:
 
 > I hope make has recompiled all necessary files; it results:
 > 
 > root@Iserver:~/gcc/libjava #
 > /root/gcc/gcc/gcj -B/root/gcc/i686-pc-linux-gnu/libjava/ -B/root/gcc/gcc/ --
 > encoding=UTF-8 -C -g -classpath /root/gcc/i686-pc-linux-gnu/libjava:. -d
 > /root/gcc/i686-pc-linux-gnu/libjava java/lang/ClassNotFoundException.java
 > // value=java/lang/ClassNotFoundException.java
 > // id=java/lang/ClassNotFoundException.java
 > // predefined_filename_p: java/lang/ClassNotFoundException.java found @8
 
 So, no more errors then. You could try to get rid of the patch in
 jcf-parse.c and then rebuild the compiler and libgcj (libgcj from
 scratch preferably.) I have the feeling that you might get further.
 
 ./A


             reply	other threads:[~2001-09-21 15:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-21 15:46 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 13:06 Alexandre Petit-Bianco
2001-09-21 11:26 Alexandre Petit-Bianco
2001-09-20  8:16 Alexandre Petit-Bianco
2001-09-19  8:26 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=20010921224601.28245.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: link
Be 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).