This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Documenting tools necessary for GCC [draft]
- From: "E. Weddington" <eric at umginc dot net>
- To: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>
- Cc: gcc at gcc dot gnu dot org
- Date: Fri, 30 May 2003 09:12:51 -0600
- Subject: Re: Documenting tools necessary for GCC [draft]
On 29 May 2003 at 20:51, Kaveh R. Ghazi wrote:
> > From: "E. Weddington" <eric@umginc.net>
> >
> > On 29 May 2003 at 13:27, Kaveh R. Ghazi wrote:
> >
> > > To develop/modify GCC (all of the above tools plus):
> > > ------------------------------------------------------
> > > GNU Bison version 1.28 (or later)
> > > Flex version 2.5.4 (or later)
> > >
> > > Necessary when modifying *.y (bison) or *.l (flex).
> > >
> > > Necessary to build GCC during development because the generated output > >
> files are not included in the cvs repository. They are included in > >
> releases. > > ------------------------------------------------------ > > IIRC,
> bison and flex were both needed to *build* gcc for the avr target on > mingw,
> not just to develop / modify. I don't know if this is a general case. > Eric
> Weddington
>
> This shouldn't be required for released versions of GCC in any
> configuration. What version of GCC were you using? Are you sure your
> timestamps were correct?
My bad. I checked last night and you're correct. I don't need bison / flex for
GCC *releases*, but they are needed to build the weekly snapshots. So I didn't
interpret your description correctly because I don't necessarily develop or
modify GCC. So perhaps this?:
To develop/modify/build snapshots of GCC (all of the above tools plus):
Sorry for my confusion.
Eric Weddington