This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: gcc will not build
On Mar 28, 2000, bryanh@giraffe-data.com (Bryan Henderson) wrote:
> Fair enough. I suggest the install instructions mention the particular
> directories where the start files and C library have to be in order for
> the build to succeed.
This would be system-specific, and, since I've been tracking GCC bugs
for years, and this is the first time I've seen a complaint like this,
I don't think it's worth the effort. Few people have libc installed
*only* in non-standard places.
Having said that, a patch for the docs to address this issue would
probably be accepted :-)
> Note that this requirement is unique to Gcc (at least, I've never had
> another build fail for this reason).
That's because GCC bootstrap actually creates 3 compiles: the stage1
compiler is built with the pre-installed compiler; the stage2 is build
with stage1, and stage3 is build with stage2, then compared with
stage2. Bootstrap is only successful if stage2 is identical to
stage3; if they differ, there's some bug lurking around in the
compiler. This, plus the fact that compiling the compiler with itself
means its own code will get optimized with any new optimizations made
available since the last release, are the reasons why we recommend
`make bootstrap' instead of plain `make'.
> Another point: I've been experimenting, and discovered that a default
> 'make' does the job OK for me
It should now be obvious why :-)
--
Alexandre Oliva Enjoy Guaranį, see http://www.ic.unicamp.br/~oliva/
Cygnus Solutions, a Red Hat company aoliva@{redhat, cygnus}.com
Free Software Developer and Evangelist CS PhD student at IC-Unicamp
oliva@{lsd.ic.unicamp.br, gnu.org} Write to mailing lists, not to me