A question about a possible build problem.

A question about a possible build problem.

[George R Goffe]

Howdy,

I'm building gcc version "gcc (GCC) 4.1.0 20050627" from cvs
successfully on my redhat enterprise linux 3 update 4 system and
then turning around and building it again with itself by repeating
the exact process via a script. The second build fails with the
following:

snip-----------

tail: cannot open `+16c' for reading: No such file or directory
tail: cannot open `+16c' for reading: No such file or directory
tail: cannot open `+16c' for reading: No such file or directory
make[1]: *** [gnucompare] Error 1
make[1]: Leaving directory `/tools/gnu/gccdev/obj.Linux.2.4.21/gcc'
make: *** [bootstrap] Error 2

Am I doing something stupid or is this a bug?

Any/all hints/tips/suggestions would be appreciated.

Thanks,

George...


=====
    _/_/_/_/ _/_/_/_/ _/_/_/_/ _/_/_/_/ _/_/_/_/ _/_/_/_/ -----
   _/       _/       _/    _/ _/    _/ _/       _/
  _/  _/_/ _/_/_/_/ _/    _/ _/_/_/_/ _/  _/_/ _/_/_/_/ -----
 _/    _/ _/       _/    _/ _/    _/ _/    _/ _/
_/_/_/_/ _/_/_/_/ _/_/_/_/ _/    _/ _/_/_/_/ _/_/_/_/ -----
"It's not what you know that hurts you, It's what you know that ain't so." Will Rogers

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Re: A question about a possible build problem.

[Zack Weinberg]

George R Goffe <grgoffe@yahoo.com> writes:

> tail: cannot open `+16c' for reading: No such file or directory
> tail: cannot open `+16c' for reading: No such file or directory
> tail: cannot open `+16c' for reading: No such file or directory

You have the buggy version of coreutils that does not recognize
old-fashioned options.  You may be able to work around this with
'export _POSIX2_VERSION=199209' (or equivalent construct if you are
using some other shell).

zw