Patch Makefile.in/Make-lang.in: create bison files atomically

Zack Weinberg zackw@Stanford.EDU
Sat Oct 14 21:54:00 GMT 2000


On Sat, Oct 14, 2000 at 02:21:28PM -0400, Kaveh R. Ghazi wrote:
>  > From: "Zack Weinberg" <zackw@Stanford.EDU>
>  > > 
>  > > IIRC, GNU packages are supposed to come with bison generated files in
>  > > the srcdir when we deliver the release version.  I believe this is to
>  > > eliminate bug reports stemming from broken bison/byacc/yacc versions.
>  > > 
>  > > We've deleted them from CVS, but the snapshots still put them there I
>  > > think and certainly the release will.
>  > 
>  > I thought the plan was to store generated copies of the files
>  > somewhere else, and copy them in at build time if we don't have bison.
>  > zw
> 
> I recall reading of such a plan, but it doesn't seem to have been
> implemented yet.  In any case, IIRC it was again only for CVS.

Doesn't stop it being generalized to the releases/snapshots.

> Snapshots and releases should provide bison files "in place" to
> confirm to GNU packaging conventions.

I don't think this particular bit of the packaging conventions is that
important, especially if we can avoid this nasty makefile kluge by
ignoring it.

The only problem with putting the generated parser off somewhere
else is if someone who doesn't have bison modifies the parser and then
their changes are ignored.  This can be dealt with by having the dummy
bison script check the age of the .y file and complain loudly if it's
newer than the generated file.

zw


More information about the Gcc-patches mailing list