fixincl.x being blown away

[Manfred Hollstein]

On Monday, 4 December 2000, 17:15:19 +0000, rearnsha@arm.com wrote:

> 
> manfredh@redhat.com said:
> > Hmm,   I  didn't  see  similar  problems   during  my   last build  on
> > armv4l-unknown-linux-gnu; I  used  sources which  were checked  out on
> > 2000/12/03 10:50:06 +0100. FWIW, I also don't have autogen installed.
> 
> 
> Hmm, thanks for the datum point.  It did fail for me on my arm-linux 
> build.
> 
> Could you answer the following?
> 
> - How did you configure gcc (current directory, absolute path, relative 
> path)?

configure flags:  --host=armv4l-unknown-linux-gnu --target=armv4l-unknown-linux-gnu --build=armv4l-unknown-linux-gnu --srcdir=../gcc-20001203 --prefix=/opt/gnu --exec-prefix=/opt/gnu/H-armv4l-linux --with-gnu-as --with-gnu-ld --disable-checking --with-local-prefix=/opt/gnu --enable-languages=c,gcov,c++ --enable-nls --verbose
BOOT_CC:	  gcc version 2.95.3 19991030 (prerelease)
BOOT_CFLAGS:	  -O2 -mcpu=strongarm110
CFLAGS:		  -O2 -mcpu=strongarm110 -fomit-frame-pointer
CXXFLAGS:	  -O2 -mcpu=strongarm110 -g

srcdir:		  /home/gnu/work/GNU/gcc-20001203
builddir:	  /home/gnu/work/GNU/gcc-20001203-armv4l-unknown-linux-gnu

> 
> - Which version of make are you using?

make-3.77-6 from the netwinder installation.

> 
> - What happens if you touch fixincl.x before building?

I don't know as the machine is currently not available; but, this
may explain things; how are you updating your tree? Are you using
the contrib/gcc_update script or similar? Or are you running plain
cvs update?

> 
> R.

Cheers, manfred