public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mike Hearn <mike@plan99.net>
To: GCC Java <java@gcc.gnu.org>
Subject: Re: Trouble building gcj 4.8.1
Date: Mon, 24 Jun 2013 16:48:00 -0000	[thread overview]
Message-ID: <CANEZrP0vTN_MAe4jOamUqKnkyXgNYJ-bsUnovANV36evGdJWPA@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP3wxTPvx5Ky2O1qds427t9LxtSt0Bm3GntjcN63_0+3rw@mail.gmail.com>

Another problem I noticed is that the class files in the source tree
don't seem to match the java files. When was the last time someone
actually ran --enable-java-maintainer-mode and checked in the results?
For instance the class file for java.lang.String is lacking the
Charset accepting c'tors, but the Java file has them??

On Mon, Jun 24, 2013 at 3:21 PM, Mike Hearn <mike@plan99.net> wrote:
> Hi there,
>
> I am trying to compile GCJ 4.8.1 with --enable-java-maintainer-mode
> (as classpath has holes in it I need to fix for my codebase to
> compile).
>
> Unfortunately this does not work and I'm unsure why. I have ecj.jar in
> the source tree.
>
> ~/gcc-build$ ../gcc-4.8.1/configure
> --prefix=/usr/local/google/home/hearn/gcc-install
> --enable-languages=java --disable-bootstrap
> --enable-java-maintainer-mode
>
> ... results in the classpath configure script failing:
>
> configure:24065: /usr/local/google/home/hearn/gcc-build/./gcc/gcj
> -B/usr/local/google/home/hearn/gcc-build/x86_64-unknown-linux-gnu/32/libjava/
> -B/usr/local/google/home/hearn/gcc-build/x86_64-unknown-linux-gnu/32/libjava/
> -B/usr/local/google/home/hearn/gcc-build/./gcc/
> -B/usr/local/google/home/hearn/gcc-install/x86_64-unknown-linux-gnu/bin/
> -B/usr/local/google/home/hearn/gcc-install/x86_64-unknown-linux-gnu/lib/
> -isystem /usr/local/google/home/hearn/gcc-install/x86_64-unknown-linux-gnu/include
> -isystem /usr/local/google/home/hearn/gcc-install/x86_64-unknown-linux-gnu/sys-include
>  -m32 -C -g  -fsource=1.5 -ftarget=1.5 Object.java
> Unrecognized option :
> -fbootclasspath=./:/usr/local/google/home/hearn/gcc-install/share/java/libgcj-4.8.1.jar
>
> Why would GCJ be unable to recognize the -fbootclasspath option?  This
> seems an obscure failure.

  reply	other threads:[~2013-06-24 16:48 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-24 13:21 Mike Hearn
2013-06-24 16:48 ` Mike Hearn [this message]
2013-06-24 17:04   ` Andrew Haley
2013-06-24 17:17     ` Mike Hearn
2013-06-24 17:26       ` Andrew Haley
2013-06-24 20:36         ` Matthias Klose
2013-06-25 13:39         ` Mike Hearn
2013-06-25 13:53           ` Mike Hearn
2013-06-25 14:07             ` Andrew Haley
2013-06-25 14:05           ` Andrew Haley
2013-06-25 14:05           ` Andrew Haley
2013-06-25 14:10             ` Mike Hearn
2013-06-25 14:12               ` Andrew Haley
2013-06-25 14:15                 ` Mike Hearn
2013-06-25 14:21                   ` Andrew Haley
2013-06-28  1:28                     ` Andïï
2013-06-28  9:06                       ` Andrew Haley
2013-07-02 14:53                     ` Bryce McKinlay
     [not found]                       ` <CANEZrP1tLxpu818cFGdgma+RVL32yRJJUOyb5m8QF=mhTZVueg@mail.gmail.com>
2013-07-03 13:43                         ` Mike Hearn
2013-07-03 13:47                           ` Andrew Haley
2013-07-03 21:31                             ` Bryce McKinlay

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=CANEZrP0vTN_MAe4jOamUqKnkyXgNYJ-bsUnovANV36evGdJWPA@mail.gmail.com \
    --to=mike@plan99.net \
    --cc=java@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).