From: Tom Tromey <tromey@redhat.com>
To: Andrew Cagney <cagney@redhat.com>
Cc: frysk <frysk@sourceware.org>
Subject: Re: .DEFAULT: rule
Date: Fri, 16 Feb 2007 01:42:00 -0000 [thread overview]
Message-ID: <m3r6srrodc.fsf@localhost.localdomain> (raw)
In-Reply-To: <45D3A21C.70300@redhat.com>
>>>>> "Andrew" == Andrew Cagney <cagney@redhat.com> writes:
Andrew> As in the contents of the .Po file?
Yes.
Andrew> below you'll see the rule being used to generate it (had to rewrite
Andrew> automake's to to work around gcj bugs). It includes -MP option to
Andrew> generate those phony rules, but they are not there.
Please file a bug report.
Andrew> # Given a .java file convert it to a .o file.
Andrew> # XXX: GCJ has a bug where it totally scrambles nested classes with
Andrew> # identical names. Reject any code with duplicate class names.
Andrew> # XXX: GCJ has a bug where, when given a -Werror fail, it still exits
Andrew> # with success. Hack around this by saving the message in a log file
Andrew> # and then checking that it is empty.
You could file these as well.
I have never heard of the second one before.
The first is probably fixed on svn trunk.
Tom
prev parent reply other threads:[~2007-02-16 1:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 19:24 Andrew Cagney
2007-02-14 21:25 ` Tom Tromey
2007-02-14 23:58 ` Andrew Cagney
2007-02-16 1:42 ` Tom Tromey [this message]
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=m3r6srrodc.fsf@localhost.localdomain \
--to=tromey@redhat.com \
--cc=cagney@redhat.com \
--cc=frysk@sourceware.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).