public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gilead at yellowhedgehog dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug java/13667] GCJ crashes on compilation
Date: Wed, 21 Jan 2004 21:42:00 -0000 [thread overview]
Message-ID: <20040121214241.28488.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040113132512.13667.gilead@yellowhedgehog.com>
------- Additional Comments From gilead at yellowhedgehog dot com 2004-01-21 21:42 -------
Exactly the same bug can be reproduced with 3.3.2, details below:
max@devel:~$ gcj -v
Reading specs from /usr/lib/gcc-lib/i486-linux/3.3.2/specs
Reading specs from /usr/lib/gcc-lib/i486-linux/3.3.2/../../../libgcj.spec
rename spec lib to liborig
Configured with: ../src/configure -v
--enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr
--mandir=/usr/share/man --infodir=/usr/share/info
--with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared --with-system-zlib
--enable-nls --without-included-gettext --enable-__cxa_atexit
--enable-clocale=gnu --enable-debug --enable-java-gc=boehm
--enable-java-awt=xlib --enable-objc-gc i486-linux
Thread model: posix
gcc version 3.3.2 (Debian)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13667
next prev parent reply other threads:[~2004-01-21 21:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-13 13:25 [Bug java/13667] New: " gilead at yellowhedgehog dot com
2004-01-13 13:34 ` [Bug java/13667] " gilead at yellowhedgehog dot com
2004-01-13 16:53 ` pinskia at gcc dot gnu dot org
2004-01-13 18:54 ` gilead at yellowhedgehog dot com
2004-01-21 19:09 ` dhazeghi at yahoo dot com
2004-01-21 21:37 ` gilead at yellowhedgehog dot com
2004-01-21 21:42 ` gilead at yellowhedgehog dot com [this message]
2004-01-21 22:09 ` dhazeghi at yahoo dot com
2004-01-22 7:05 ` gilead at yellowhedgehog dot com
2004-01-24 15:54 ` dhazeghi at yahoo dot com
2004-01-25 16:28 ` gilead at yellowhedgehog dot com
2004-01-25 16:31 ` pinskia at gcc dot gnu dot org
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=20040121214241.28488.qmail@sources.redhat.com \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).