From: Gerald Pfeifer <gerald@pfeifer.com>
To: Mike Stump <mrs@apple.com>
Cc: gcc@gcc.gnu.org, java@gcc.gnu.org, David O'Brien <obrien@freebsd.org>
Subject: Re: configure, CFLAGS, and libjava
Date: Sun, 14 Nov 2004 00:05:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.61.0411140100380.90337@acrux.dbai.tuwien.ac.at> (raw)
In-Reply-To: <2ED5BE2A-35CC-11D9-822C-003065BDF310@apple.com>
On Sat, 13 Nov 2004, Mike Stump wrote:
> Not limited to libjava... All of it is, uhm, what's the word, unfortunate.
> It triggers too often, and just doesn't do the right thing, an rm -rf
> followed by another build would be preferable, as then it would actually
> build all the time.
Well, it is much worse than that! For libjava, this failure reproducibly
happens when building in a pristine build tree from pristine sources.
Gerald
next prev parent reply other threads:[~2004-11-14 0:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-13 20:37 Gerald Pfeifer
2004-11-13 23:47 ` Mike Stump
2004-11-14 0:05 ` Gerald Pfeifer [this message]
2004-11-15 12:05 ` Rainer Orth
2004-11-23 2:54 ` 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=Pine.BSF.4.61.0411140100380.90337@acrux.dbai.tuwien.ac.at \
--to=gerald@pfeifer.com \
--cc=gcc@gcc.gnu.org \
--cc=java@gcc.gnu.org \
--cc=mrs@apple.com \
--cc=obrien@freebsd.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).