This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: gcc-ss-20011203 is now available
- From: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
- To: Phil Edwards <pedwards at disaster dot jaj dot com>
- Cc: <guerby at acm dot org>, <schwab at suse dot de>, <gcc at gcc dot gnu dot org>
- Date: Tue, 4 Dec 2001 20:36:41 +0000 (GMT)
- Subject: Re: gcc-ss-20011203 is now available
On Tue, 4 Dec 2001, Phil Edwards wrote:
> look at maintainer-scripts/crontab
> look at wall clock
> if TIME near Sunday 4:40 PM Pacific timezone
Monday.
> Doesn't gcc_release do a build in order to ensure the generated source
> files are there? It's certainly no guarantee, but it should prevent
> snapshots from going out that don't build on, say, i596-linux.
It only does a build for releases, not snapshots. Given the load on
gcc.gnu.org, doing a build for snapshots does not seem wise. Instead we
simply require people building from snapshots to have the necessary tools
intalled to build generated files they'd need when building from CVS.
Besides, patching generated files that aren't in CVS doesn't really work
well - there isn't a "release mode" for gcc_update that will clean up
timestamps on (say) Bison-generated files after applying a patch, despite
those files being in CVS and so not meant to be touched for CVS checkouts.
Including Info and Bison-generated files would also substantially bulk up
diffs.
--
Joseph S. Myers
jsm28@cam.ac.uk