From: Tom Tromey <tromey@redhat.com>
To: "Richard Guenther" <richard.guenther@gmail.com>
Cc: "Andreas Tobler" <andreast-list@fgznet.ch>,
"Ralf Wildenhues" <Ralf.Wildenhues@gmx.de>,
"Gcc Patch List" <gcc-patches@gcc.gnu.org>
Subject: Re: Patch: automatic dependencies for gcc
Date: Thu, 27 Mar 2008 15:45:00 -0000 [thread overview]
Message-ID: <m3myokfdxq.fsf@fleche.redhat.com> (raw)
In-Reply-To: <84fc9c000803270353u1a2ddec8pf4edf2ecee753822@mail.gmail.com> (Richard Guenther's message of "Thu\, 27 Mar 2008 11\:53\:33 +0100")
Richard> If you touch Makefile.in and then do make -j2 cc1, make goes
Richard> into an infinite loop for me (3.81).
Well, this looks really bad. I think this is a GNU make bug:
https://savannah.gnu.org/bugs/?3330
https://savannah.gnu.org/bugs/?func=detailitem&item_id=15919
Our circumstances aren't identical to what is in those reports, but
the symptoms are the same. This is fixed in cvs, but that won't do us
any good until there is a make release and then time for that release
to get out to everybody.
I am not sure what to do. I tried a few attempts to work around the
bug, but I couldn't make it work. I'm out of ideas for fixes.
I'll prepare a patch to revert this change. Let me know what you think.
Tom
next prev parent reply other threads:[~2008-03-27 15:15 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-07 21:15 Tom Tromey
2008-03-07 23:20 ` Joseph S. Myers
2008-03-07 23:28 ` Tom Tromey
2008-03-08 0:37 ` Ralf Wildenhues
2008-03-08 0:42 ` Tom Tromey
2008-03-08 14:33 ` Ralf Wildenhues
2008-03-08 16:20 ` Tom Tromey
2008-03-08 16:36 ` Ralf Wildenhues
2008-03-08 18:41 ` Ralf Wildenhues
2008-03-08 19:42 ` Tom Tromey
2008-03-09 14:40 ` Ralf Wildenhues
2008-03-09 15:07 ` Ralf Wildenhues
2008-03-09 16:02 ` Tom Tromey
2008-03-09 16:36 ` Ralf Wildenhues
2008-03-09 16:55 ` Tom Tromey
2008-03-11 0:01 ` Ben Elliston
2008-03-11 0:11 ` Tom Tromey
2008-03-18 14:35 ` Paolo Bonzini
2008-03-21 13:43 ` Tom Tromey
2008-03-21 17:43 ` Paolo Bonzini
2008-03-24 20:34 ` Tom Tromey
2008-03-25 8:33 ` Tom Tromey
2008-03-25 8:42 ` Paolo Bonzini
2008-03-25 15:43 ` Tom Tromey
2008-03-25 16:32 ` Paolo Bonzini
2008-03-25 17:27 ` Tom Tromey
2008-03-25 17:28 ` Tom Tromey
2008-03-25 17:29 ` Paolo Bonzini
2008-03-25 17:39 ` Tom Tromey
2008-03-25 18:00 ` Tom Tromey
2008-03-25 20:41 ` Ralf Wildenhues
2008-03-25 20:51 ` Tom Tromey
2008-03-25 21:03 ` Ralf Wildenhues
2008-03-26 2:08 ` Tom Tromey
2008-03-25 22:26 ` Andreas Tobler
2008-03-26 3:26 ` Tom Tromey
2008-03-26 13:16 ` Richard Guenther
2008-03-26 13:17 ` Tom Tromey
2008-03-26 13:21 ` Richard Guenther
2008-03-26 13:53 ` Tom Tromey
2008-03-26 15:05 ` Basile STARYNKEVITCH
2008-03-26 15:27 ` Tom Tromey
2008-03-26 16:47 ` Basile STARYNKEVITCH
2008-03-27 12:02 ` Richard Guenther
2008-03-27 15:45 ` Tom Tromey [this message]
2008-03-27 16:40 ` Tom Tromey
2008-03-27 17:14 ` Richard Guenther
2008-03-27 17:41 ` Tom Tromey
2008-03-27 18:34 ` Mark Mitchell
2008-03-27 19:39 ` Tom Tromey
2008-03-27 19:45 ` Diego Novillo
2008-03-27 20:07 ` Tom Tromey
2008-03-27 20:16 ` Diego Novillo
2008-03-27 20:31 ` Paolo Bonzini
2008-03-27 20:20 ` David Daney
2008-03-27 21:42 ` Tom Tromey
2008-03-27 22:43 ` Ralf Wildenhues
2008-03-27 22:47 ` Tom Tromey
2008-03-27 19:21 ` Paolo Bonzini
2008-03-25 21:00 ` Tom Tromey
2008-03-25 21:07 ` Ralf Wildenhues
2008-03-25 21:44 ` Tom Tromey
2008-03-20 16:54 ` Tom Tromey
2008-03-27 16:41 Dominique Dhumieres
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=m3myokfdxq.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=Ralf.Wildenhues@gmx.de \
--cc=andreast-list@fgznet.ch \
--cc=gcc-patches@gcc.gnu.org \
--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).