From: Tom Tromey <tromey@redhat.com>
To: "Richard Guenther" <richard.guenther@gmail.com>
Cc: "Mark Mitchell" <mark@codesourcery.com>,
"Gcc Patch List" <gcc-patches@gcc.gnu.org>,
"Java Patch List" <java-patches@gcc.gnu.org>
Subject: Re: Patch: Remove fastjar
Date: Fri, 26 May 2006 12:42:00 -0000 [thread overview]
Message-ID: <m3k689m08t.fsf@localhost.localdomain> (raw)
In-Reply-To: <84fc9c000605260424p2d255c3ex577f9e8f30a9182a@mail.gmail.com>
>>>>> "Richard" == Richard Guenther <richard.guenther@gmail.com> writes:
Richard> Now, the fastjar removal is a desaster.
Yup.
Richard> This suggests that fastjar is really not a separate package
Richard> from gcc. (It requires libiberty, its documentation requires
Richard> all sorts of gcc texi magic which I couldn't get right
Yes, nobody has had the motivation to fix fastjar's configury. It
probably isn't hard to do. If you're interested, tell me your
savannah user id and I will give you write access.
Tom
next prev parent reply other threads:[~2006-05-26 12:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-30 23:00 Tom Tromey
2006-03-30 23:06 ` Andrew Pinski
2006-03-31 18:19 ` Tom Tromey
2006-03-31 18:40 ` DJ Delorie
2006-04-03 23:21 ` Tom Tromey
2006-03-30 23:12 ` David Daney
2006-03-30 23:29 ` Andrew Pinski
2006-03-30 23:57 ` Mark Wielaard
2006-03-31 0:29 ` Per Bothner
2006-03-31 11:09 ` Mark Wielaard
2006-03-31 17:16 ` Bryce McKinlay
2006-03-31 17:26 ` Per Bothner
2006-03-31 19:27 ` Bryce McKinlay
2006-03-31 19:39 ` Per Bothner
[not found] ` <e0inac$vgh$1@sea.gmane.org>
2006-03-31 13:47 ` [RFC] jar shell script (was Re: Patch: Remove fastjar) Paolo Bonzini
2006-03-31 14:02 ` Paolo Bonzini
2006-03-31 18:24 ` Patch: Remove fastjar Tom Tromey
2006-03-31 18:21 ` Tom Tromey
2006-04-04 0:12 ` Tom Tromey
2006-03-31 23:43 ` Mark Mitchell
2006-05-26 11:24 ` Richard Guenther
2006-05-26 12:33 ` Andrew Haley
2006-05-26 12:42 ` Tom Tromey [this message]
2006-04-01 9:30 ` Laurent GUERBY
2006-04-04 0:18 ` Tom Tromey
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=m3k689m08t.fsf@localhost.localdomain \
--to=tromey@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=java-patches@gcc.gnu.org \
--cc=mark@codesourcery.com \
--cc=richard.guenther@gmail.com \
/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).