This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
may be a typo somewhere in the gcc4 build files?
- From: Bob Gustafson <bobgus at rcn dot com>
- To: gcc at gcc dot gnu dot org
- Date: Tue, 28 Dec 2004 10:32:51 -0600
- Subject: may be a typo somewhere in the gcc4 build files?
- Reply-to: bobgus at rcn dot com
I have been trying to build from the gcc4 snapshot files, and succeeding
occasionally. (for example gcc-4.0-20041226)
./configure \
--enable-languages=c,c++,f95 \
--disable-nls \
--enable-werror \
--enable-checking \
2>&1 | tee config.out
make 2>&1 | tee make.out
The build moves along and then encounters a problem:
make[1]: Entering directory `/usr/local/src/gcc/gcc-4.0-20041226/build-
i686-pc-linux-gnu/libiberty'
make[1]: *** No rule to make target `../include/ansidecl.h', needed by
`regex.lo'. Stop.
The file ansidecl.h does exist, but it is one directory higher. (i.e.,
looking for ../../include/ansidecl.h would succeed.
The commands:
cd build* ; mkdir include ; cp ../include/* include
allows the compile to get over that problem and a few additional
accesses to wayward .h files.
Later on, the 'install-sh' file is in the wrong place. I copy it to the
'right' place and proceed.
A little bit further, I get:
make[1]: *** No rule to make target `../libiberty/libiberty.a', needed
by `full-stamp'. Stop.
make[1]: Leaving directory `/usr/local/src/gcc/gcc-4.0-20041226/build-
i686-pc-linux-gnu/fixincludes'
make: *** [all-build-fixincludes] Error 2
Again, the file libiberty.a does exist, just not in the place where the
make script is looking for it.
In one of the command lines, I saw an argument '-I./../include'
If there was an additional '.' following the -I, it would work.
Don't seem to find it right now - may not be the source of the problem
anyway.
-------
These seemingly 'wrong place' file problems have been there for the last
couple of months of occasional forays into gcc4 snapshot files.
Should I be doing something differently?