public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: <guerby@acm.org>
To: jsm28@cam.ac.uk
Cc: zack@codesourcery.com, bosch@gnat.com, minyard@acm.org, gcc@gcc.gnu.org
Subject: Re: Ada build now requires gnatmake?
Date: Tue, 04 Dec 2001 11:46:00 -0000	[thread overview]
Message-ID: <200112041936.fB4JaiY29839@ulmo.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.33.0112041928210.23234-100000@kern.srcf.societies.cam.ac.uk> (jsm28@cam.ac.uk)

> I thought that the generated files were now mentioned in
> contrib/gcc_update, so if you update with that or use contrib/gcc_update
> --touch after updating you shouldn't see the problem.

You'll get not-in-synch generated files, so you'll probably either
won't be able to build or build a non-functional compiler. It is my
understanding that gcc_update is intended just to make sure timestamp
are rights before making a release tarball, but it can't make sure
sources are right :).

-- 
Laurent Guerby <guerby@acm.org>

  reply	other threads:[~2001-12-04 19:46 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
2001-12-04 11:40     ` Joseph S. Myers
2001-12-04 11:46       ` guerby [this message]
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=200112041936.fB4JaiY29839@ulmo.localdomain \
    --to=guerby@acm.org \
    --cc=bosch@gnat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jsm28@cam.ac.uk \
    --cc=minyard@acm.org \
    --cc=zack@codesourcery.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).