public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: jddahl <jddahl@micron.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: RE: libgcj/2715: Can't compile on Redhat 6.2 Date: Thu, 03 May 2001 09:36:00 -0000 [thread overview] Message-ID: <20010503163600.23574.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR libgcj/2715; it has been noted by GNATS. From: jddahl <jddahl@micron.com> To: "'tromey@redhat.com'" <tromey@redhat.com>, jddahl <jddahl@micron.com> Cc: gcc-gnats@gcc.gnu.org Subject: RE: libgcj/2715: Can't compile on Redhat 6.2 Date: Thu, 3 May 2001 10:35:31 -0600 That was it! Thanks. When trying to compile with the following command: gcj -c -d /u/jddahl/java/objects.linux/test/core /u/jddahl/java/sources/test/core/InitializationException.java the .o file is place in the current directory, not /u/jddahl/java/objects.linux/test/core. Is there a fix? Thanks, Jeff -----Original Message----- From: Tom Tromey [ mailto:tromey@redhat.com ] Sent: Wednesday, May 02, 2001 2:06 PM To: jddahl@micron.com Cc: gcc-gnats@gcc.gnu.org Subject: Re: libgcj/2715: Can't compile on Redhat 6.2 >>>>> ">" == jddahl <jddahl@micron.com> writes: >> Originator: jddahl@micron.com >> Redhat 6.2 >> ../../../../gcc/libjava/resolve.cc: In function `_Jv_word >> _Jv_ResolvePoolEntry(java::lang::Class*, int)': >> ../../../../gcc/libjava/resolve.cc:134: Internal compiler error in >> c_expand_expr, at c-common.c:4271 You don't say what snapshot you are using. I believe this particular bug was fixed sometime yesterday. Could you try a more recent snapshot? Tom
next reply other threads:[~2001-05-03 9:36 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-05-03 9:36 jddahl [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-05-03 11:26 jddahl 2001-05-03 10:46 Tom Tromey 2001-05-02 12:56 Tom Tromey 2001-05-02 10:16 jddahl
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=20010503163600.23574.qmail@sourceware.cygnus.com \ --to=jddahl@micron.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).