From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: Loren James Rittle <rittle@latour.rsch.comm.mot.com>
Cc: <gcc@gcc.gnu.org>
Subject: Re: Bison 1.75c + FreeBSD 5.0 = can't boostrap gcc from CVS
Date: Fri, 13 Dec 2002 12:06:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0212131901340.16119-100000@kern.srcf.societies.cam.ac.uk> (raw)
In-Reply-To: <200212130016.gBD0G4FO080957@latour.rsch.comm.mot.com>
On Thu, 12 Dec 2002, Loren James Rittle wrote:
> No more investigatation required. There is no "touch rule" for
> gcc/intl/plural.[yc] in contrib/gcc_update. Thus, any particular
> initial checkout/update from CVS could have the time stamps out of
> order. The only reason the population of developers doesn't see this
> issue (even if they have upgraded bison to a recent FSF release ala
> 1.75), is that gcc/intl hasn't been updated since long before that
> release.
It appears that Gerald's patch
<http://gcc.gnu.org/ml/gcc-patches/2002-12/msg00370.html> hasn't yet been
reviewed.
> We could catch these problem much earlier if we removed *all* derived
> files from CVS and never added built files to srcdir during a normal
> bootstrap...
This file shouldn't be in CVS as a Bison-generated file, except that the
release script adds Bison-generated files to the source directory by doing
a bootstrap and this won't work for the intl directory because that
directory doesn't get built at all on systems with GNU libintl in libc.
The normal rule for what goes in CVS remains that it should be exactly the
files not removed by "make maintainer-clean", which should be all files
needed to configure and build plus some files created by more specialised
tools (e.g. autogen) or tools with tight version dependencies, plus
generated Texinfo files for update_web_docs.
--
Joseph S. Myers
jsm28@cam.ac.uk
next prev parent reply other threads:[~2002-12-13 19:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-11 21:15 Craig Rodrigues
2002-12-12 11:52 ` Joseph S. Myers
2002-12-12 17:18 ` Loren James Rittle
2002-12-13 12:06 ` Joseph S. Myers [this message]
2002-12-27 7:45 ` Gerald Pfeifer
2002-12-29 14:15 ` PATCH contrib/gcc_update (was: Bison 1.75c + FreeBSD 5.0 = can't boostrap gcc from CVS) Gerald Pfeifer
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=Pine.LNX.4.33.0212131901340.16119-100000@kern.srcf.societies.cam.ac.uk \
--to=jsm28@cam.ac.uk \
--cc=gcc@gcc.gnu.org \
--cc=rittle@latour.rsch.comm.mot.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).