public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Matthias Klose <doko@ubuntu.com>
To: Andrew John Hughes <gnu_andrew@member.fsf.org>
Cc: java@gcc.gnu.org
Subject: Re: [classpath-0.98 merge branch] update and status
Date: Mon, 15 Sep 2008 12:21:00 -0000	[thread overview]
Message-ID: <48CE5319.5090807@ubuntu.com> (raw)
In-Reply-To: <20080914233618.GA30546@rivendell.middle-earth.co.uk>

Andrew John Hughes schrieb:
> On 21:56 Sun 14 Sep     , Matthias Klose wrote:
>> Merged trunk into the classpath merge branch.
>>
>> Imported new classpath snapshot into the merge branch:
>>
>>  - Reverted the Thread optimization (does require gcj local changes,
>>    and I did run out of time).
>>
>>  - Don't explicitely configure with --disable-gjdoc. This needs
>>    configuration with --with-antlr-jar as well.
>>
>>  - For ANTLR, the classpath configury wants a JAVA runtime (which
>>    currently is not configured/set). I added a check for the binary
>>    runantlr, which may be Debian/Ubuntu specific). Did not yet check,
>>    what is needed to run the installed gjdoc.
>>
> 
> At present, the build fails for me because I don't have a 'runantlr'.
> How do we handle other such dependencies like gjavah?

in maintainer mode, you are expected to have them. That's the case for gjavah
and ecj1. But we need an antlr binary for a normal build as well if we do
configure with --enable-gjdoc. Or we have to check for any "JAVA" interpreter
and disable gjdoc if we cannot find one.

  Matthias

  reply	other threads:[~2008-09-15 12:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <48CD6C5B.70201@ubuntu.com>
2008-09-14 23:37 ` Andrew John Hughes
2008-09-15 12:21   ` Matthias Klose [this message]
2008-09-28 15:32   ` Matthias Klose
2008-09-28 21:35     ` Andrew John Hughes
2008-09-29  0:20       ` Matthias Klose

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=48CE5319.5090807@ubuntu.com \
    --to=doko@ubuntu.com \
    --cc=gnu_andrew@member.fsf.org \
    --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).