🚀 go-pugleaf

ERNIM@ioc.unibe.CH (MARKUS TARKOEY) writes:

>`make LANGUAGES=C' (there were some error messages like the following
>fixproto: cpp could not parse /usr/people/logo/gcc-2.5.3/include/DPS/XDPSlib.h
>(I thought whis would not be a problem as you mentioned that error messages
>could appear)
>
>`make stage1'
>This command gave me a bundle of error messages:
>mv: stamp-proto: No such file or directory.
>mv: gcc-cross: No such file or directory.  
>mv: g++-cross: No such file or directory.  
>mv: cc1plus: No such file or directory.    
>mv: cc1obj: No such file or directory.     
>mv: protoize: No such file or directory.   
>mv: unprotoize: No such file or directory.
>
>OK. Now the question is what did I understand wrong in your installation
>procedure? After successful compiling I wanted to transfer the whole thing
>back to my own machine and do the `make install'.
>Can you help me ?

The errors above are normal.  Just ignore them, and continue.
When you specify "make LANGUAGES=C", some files such as the C++ front-end
(cc1plus) don't get built.

Here's a script I use to build gcc.  It goes through the various
stages, redirecting their output to files, and continuing to the
next stage only if the previous stage succeeded.

#!/bin/sh
./configure > ERRS.configure 2>&1 &&
make CC=gcc CFLAGS=-O LANGUAGES=c > ERRS.make 2>&1 &&
make stage1 > ERRS.stage1 2>&1 &&
make CC="stage1/xgcc -Bstage1/" CFLAGS=-O2 > ERRS.make2 2>&1 &&
make stage2 > ERRS.stage2 2>&1 &&
make CC="stage2/xgcc -Bstage2/" CFLAGS=-O2 > ERRS.make3 2>&1 &&
make compare > ERRS.compare 2>&1 &&
make CC="stage2/xgcc -Bstage2/" CFLAGS=-O2 install > ERRS.make_install 2>&1 &&
true

-- 
Fergus Henderson                     fjh@munta.cs.mu.OZ.AU