This is the mail archive of the
mailing list for the GCC project.
Re: Cannot build mainline gcc on x86 linux
- From: Kelley Cook <kcook34 at ford dot com>
- To: Nathanael Nerode <neroden at twcny dot rr dot com>
- Cc: gcc at gcc dot gnu dot org, "Sysoltsev, Vyatcheslav" <vyatcheslav dot sysoltsev at intel dot com>, Matt Kraai <kraai at alumni dot cmu dot edu>
- Date: Mon, 11 Aug 2003 11:52:42 -0400
- Subject: Re: Cannot build mainline gcc on x86 linux
- Hop-count: 1
- References: <833299AC3C8D9B4D8F28F0823979DE850D8827@nnsmsx401.inn.intel.com> <20030809191257.GA1480@ftbfs.org>
- Reply-to: Kelley Cook <KelleyCook at wideopenwest dot com>
Matt Krai wrote:
When I regenerated Makefile.in, it lost the following targets:
I don't know why they were there in the first place, nor whether
adding them back will fix your problem.
From perusing the CVS archive, these targets showed up on July 13th from this commit:
which was discussed at http://gcc.gnu.org/ml/gcc-patches/2003-07/msg01231.html
Maybe, of course, I am missing something simple, but I don't see where those new
targets came from since the corresponding targets were not in the Makefile.tpl
committed at the same time. In addition, when I regenerate Makefile.in with autogen
1.5.5, I see no differences compared to the version that is in the mainline.
Note that Slava is now getting a build-in-source-tree bootstrap error without the
This leads to three releated questions:
a) Are Matt and I doing something incorrect to generate Makefile.in?
b) ... or should not the additional targets ever have been there?
C) ... or should they actually exist and somehow the upstream changes never were committed?
Thanks for any suggestions you can give on this matter.