public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Nathanael Nerode <neroden@twcny.rr.com>
Cc: Paolo Bonzini <bonzini@gnu.org>, gcc-patches@gcc.gnu.org
Subject: Re: [toplevel bootstrap PATCH] Add profiledbootstrap
Date: Wed, 09 Jun 2004 05:41:00 -0000	[thread overview]
Message-ID: <20040609040014.GA28274@nevyn.them.org> (raw)
In-Reply-To: <40C67425.4000001@twcny.rr.com>

On Tue, Jun 08, 2004 at 10:21:25PM -0400, Nathanael Nerode wrote:
> Paolo Bonzini wrote:
> >This patch adds toplevel profiledbootstrap.
> >
> >Since this makes stage1 have multiple descendants, I had to abandon
> >the prev/next scheme to link bootstrap-stages.
> >
> >Instead, I either specify dependancies separately or  use double-colon
> >rules, 
> The top level isn't allowed to use GNU make, IIRC -- aren't double-colon 
> rules a GNU makeism?  :-P  Or are they portable?
> 
> (And isn't this a nightmare?  Thanks for your work.)

Even if they are a GNU makeism, the question is whether they'll cause
parse errors in other Make implementations - the bootstrap rules belong
to GCC.

The GNU make manual does not list them as an extension, so I assume
they are at least a little portable...

-- 
Daniel Jacobowitz

  reply	other threads:[~2004-06-09  4:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-03 10:50 Paolo Bonzini
2004-06-09  3:24 ` Nathanael Nerode
2004-06-09  5:41   ` Daniel Jacobowitz [this message]
2004-06-09  6:17     ` Ian Lance Taylor
2004-06-09  9:47     ` Paolo Bonzini
2004-06-09 10:45       ` Paolo Bonzini
2004-06-09 10:55   ` Paolo Bonzini
2004-06-09 13:28 Nathanael Nerode

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=20040609040014.GA28274@nevyn.them.org \
    --to=drow@false.org \
    --cc=bonzini@gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=neroden@twcny.rr.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).