public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joe Buck <jbuck@synopsys.COM>
To: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
Cc: minyard@acm.org, gcc@gcc.gnu.org
Subject: Re: Ada build now requires gnatmake?
Date: Tue, 04 Dec 2001 16:49:00 -0000	[thread overview]
Message-ID: <200112050049.QAA17255@atrus.synopsys.com> (raw)
In-Reply-To: <10112050002.AA19011@vlsi1.ultra.nyu.edu> from "Richard Kenner" at Dec 04, 2001 07:02:49 PM


>     I just did an update and tried a bootstrap, and it seems that gnatmake
>     is used to build the Ada compiler, specifically to build treeprs.ads,
>     einfo.h, sinfo.h, and nmake.adb.  I thought bootstrapping was only
>     supposed to require the compiler and gnatbind.

Kenner writes:

> Those files are in the tree, but you may have to do a "touch" if they are older
> than what they depend on.

Perhaps contrib/gcc_update should be updated to take care of this?  It
already does the same for other such files where the derived file is
in the tree.



  reply	other threads:[~2001-12-05  0:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-04 16:08 Richard Kenner
2001-12-04 16:49 ` Joe Buck [this message]
2001-12-05  4:30   ` guerby
  -- strict thread matches above, loose matches on Subject: below --
2001-12-04 13:25 dewar
2001-12-04 10:56 Corey Minyard
2001-12-04 11:15 ` Geert Bosch
2001-12-04 11:22   ` Zack Weinberg
2001-12-04 11:40     ` Joseph S. Myers
2001-12-04 11:46       ` guerby
2001-12-04 11:51         ` Joseph S. Myers
2001-12-04 11:56       ` Geert Bosch
2001-12-04 12:24     ` guerby
2001-12-04 12:28       ` Geert Bosch
2001-12-04 13:23         ` guerby
2001-12-04 14:32           ` Florian Weimer
2001-12-04 14:58             ` guerby
2001-12-04 15:06               ` Geert Bosch

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=200112050049.QAA17255@atrus.synopsys.com \
    --to=jbuck@synopsys.com \
    --cc=gcc@gcc.gnu.org \
    --cc=kenner@vlsi1.ultra.nyu.edu \
    --cc=minyard@acm.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).