public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug java/30292] ICE on compiling .java by gcc(1)
Date: Tue, 26 Dec 2006 13:08:00 -0000	[thread overview]
Message-ID: <20061226130833.7221.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30292-12292@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from pinskia at gcc dot gnu dot org  2006-12-26 13:08 -------
No, compiling .java should work with the gcc driver and if it does not, then
there is a bug there.  And we should not error out.

Also the ICE is a bug which needs to fixed seperately from the "driver" issue
anyways.

The result without the ICE is not confusing at all:

Without ICE the result would be still confusing at least to most
C/C++/Fortran/Ada programmers :):
/usr/lib/gcc/x86_64-redhat-linux/4.1.1/../../../../lib64/crt1.o: In function
`_start':
(.text+0x20): undefined reference to `main'

that means you did not include a main function.

hello.java:(.text+0x12): undefined reference to `_Jv_InitClass'
that means you did not include the library libgcj.  These are all normal common
problems for beginner programmers.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30292


  parent reply	other threads:[~2006-12-26 13:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-26  5:37 [Bug driver/30292] New: " jan dot kratochvil at redhat dot com
2006-12-26  5:38 ` [Bug driver/30292] " jan dot kratochvil at redhat dot com
2006-12-26 13:08 ` pinskia at gcc dot gnu dot org [this message]
2006-12-26 20:55 ` [Bug java/30292] " tromey at gcc dot gnu dot org
2006-12-27  2:52 ` pinskia at gcc dot gnu dot org
2006-12-27 11:14 ` tromey at gcc dot gnu dot org
2007-01-29 20:03 ` tromey 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=20061226130833.7221.qmail@sourceware.org \
    --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).