This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Now GCC is really hosed...
- To: Mark Mitchell <mark at codesourcery dot com>
- Subject: Re: Now GCC is really hosed...
- From: Bruce Korb <bkorb at sco dot COM>
- Date: Wed, 12 Jul 2000 13:33:51 -0700
- CC: GNU Compiler <gcc at gcc dot gnu dot org>, bkorb at sco dot COM
- Organization: Santa Cruz Operations
- References: <396C8726.5FB28BB6@sco.com> <20000712101709W.mitchell@codesourcery.com> <396CB83E.8ACD132B@sco.com> <20000712114615J.mitchell@codesourcery.com>
Mark Mitchell wrote:
> Bruce> OpenServer 5. Whatever. Moving these now deleted
> Bruce> generated files to the contrib directory would not be
> Bruce> terrible. The missing script could go off and look there
> Bruce> for the current version. Warning the user, of course :-).
> Bruce> Wanna patch and a cron daemon to update the contrib dir?
> Bruce> Give me a weekend or two.
>
> That seems like a good idea, along the lines of what Richard was
> suggesting. Perhaps we could make a directory `genfiles' or some
> such, rather than putting this stuff in contrib?
>
> If you're willing to put the machinery together, that would be great!
OK. Here's the proposal:
1. Under {egcs|gcc} create a directory "gen" (keeping it the same
length as "gcc" :) that contains generated sources. The structure
would be identical to that of gcc. I.e.:
gcc/fixinc/fixincl.x
gets moved to:
gen/fixinc/fixincl.x
2. The configure script determines whether or not certain tools
exist with the right features (e.g. "perf"). Anything "missing"
will cause the tool be mapped to a missing script that copies
out the right source (assuming a consistent CVS snapshot.
Its the best you can do.) and warns the builder that life might
be easier if the correct tool were installed.
3. The normal build mechanism will invoke the configured tool or
alternate script.
4. sourceware.cygnus.com will run a cron daemon (that I will write)
that runs every {1|4|6|...|24} hours that looks at time stamps
of the predecessor files for the generated files. Should one
be more recent, then the generated file is reconstructed and
checked in. Committers would be invited to do this themselves
when they do their deed, but the cron daemon would make it
non-mandatory. Provision would be made for non-main branch
commits (viz. named branch commits would be done on the same
named branch, unnamed branch commits would be ignored. Perforce.)
This won't be ready tomorrow.