public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com>
To: Geert Bosch <bosch@gnat.com>
Cc: Corey Minyard <minyard@acm.org>, gcc@gcc.gnu.org
Subject: Re: Ada build now requires gnatmake?
Date: Tue, 04 Dec 2001 11:22:00 -0000	[thread overview]
Message-ID: <20011204192241.GG19450@codesourcery.com> (raw)
In-Reply-To: <4DDC9261-E8EB-11D5-8627-00039344BF4A@gnat.com>

On Tue, Dec 04, 2001 at 02:15:39PM -0500, Geert Bosch wrote:
> 
> On Tuesday, December 4, 2001, at 01:57 , Corey Minyard wrote:
> 
> >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.
> 
> Yes, you're right. I have checked in a patch to einfo.ads and forgot
> to update the dependent sources, and sinced I have gnatmake on my
> system this didn't show up during bootstrap. I'll fix this and think
> about ways to ensure this doesn't happen again.

I thought the generated files had been taken out of CVS?

My offer to rewrite the generator programs in C stands.

zw

  reply	other threads:[~2001-12-04 19:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-04 10:56 Corey Minyard
2001-12-04 11:15 ` Geert Bosch
2001-12-04 11:22   ` Zack Weinberg [this message]
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
2001-12-04 13:25 dewar
2001-12-04 16:08 Richard Kenner
2001-12-04 16:49 ` Joe Buck
2001-12-05  4:30   ` guerby

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=20011204192241.GG19450@codesourcery.com \
    --to=zack@codesourcery.com \
    --cc=bosch@gnat.com \
    --cc=gcc@gcc.gnu.org \
    --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).