This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
RE: "make -j 2 bootstrap" gives problem with gcc-3.0.1
- To: gcc-help at gcc dot gnu dot org
- Subject: RE: "make -j 2 bootstrap" gives problem with gcc-3.0.1
- From: "Karthikeyan M. D" <dkarthik at wilco-int dot com>
- Date: Thu, 23 Aug 2001 09:34:37 +0530
Hi,
Thanks for the reply. It worked after installing the packages
autogen and flex. These two were missing earlier.
Regards,
Karthik
> -----Original Message-----
> From: Alexandre Oliva [SMTP:aoliva@redhat.com]
> Sent: Wednesday, August 22, 2001 12:55
> To: Karthikeyan M. D
> Cc: gcc-help@gcc.gnu.org
> Subject: Re: "make -j 2 bootstrap" gives problem with gcc-3.0.1
>
> On Aug 21, 2001, "Karthikeyan M. D" <dkarthik@wilco-int.com> wrote:
>
> > I applied the patch
> > gcc-3.0-3.0.1.diff to gcc-3.0 (patch -p1 < gcc-3.0-3.0.1.diff), tried
> > building it and it end with the below mentioned error. Am I applying the
> > patch correctly
>
> Yep, but you should run contrib/gcc_update --touch after installing
> the patch, so that generated files don't appear to be older than their
> sources. But this is only going to work if the generated files are
> included in the diffs; I'm not sure they are. If they aren't, you're
> going to need GCC development tools such as AutoGen, and possibly
> bison, flex, etc, to be able to build GCC. Alternatively, download
> the full tarball, that contains the built files and whose timestamps
> should all be correct.
>
> --
> Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
> Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
> CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
> Free Software Evangelist *Please* write to mailing lists, not to me
This message is confidential and may also be legally privileged. If you are not the intended recipient, please notify us immediately. You should not copy it or use it for any purpose, nor disclose it's contents to any other person. The views and opinions expressed in this e-mail message are the author's own and may not reflect the views and opinions of Wilco International.