I installed 5.0-R on my new alpha (Thanks Wilko!) and tried to run
a buildworld.  It explodes in make depend in cpp0:

#cd /usr/src/gnu/usr.bin/cc/cpp0
#make obj
#make depend
[...]
mkdep -f .depend -a    -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\"/usr\" -I/usr/obj/usr
/src/gnu/usr.bin/cc/cpp0/../cc_tools -I/usr/src/gnu/usr.bin/cc/cpp0/../cc_tools 
-I/usr/src/gnu/usr.bin/cc/cpp0/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc
/cpp0/../../../../contrib/gcc/config  /usr/src/gnu/usr.bin/cc/cpp0/../../../../c
ontrib/gcc/cppmain.c c-parse+%DIKED.c /usr/src/gnu/usr.bin/cc/cpp0/../../../../c
ontrib/gcc/c-lang.c /usr/src/gnu/usr.bin/cc/cpp0/../../../../contrib/gcc/c-decl.
c
/usr/src/contrib/gcc/cppmain.c:24:20: config.h: No such file or directory
In file included from /usr/src/contrib/gcc/cppmain.c:25:
/usr/src/contrib/gcc/system.h:110:24: safe-ctype.h: No such file or directory
In file included from /usr/src/contrib/gcc/hashtable.h:21,
                 from /usr/src/contrib/gcc/cpplib.h:27,
                 from /usr/src/contrib/gcc/cppmain.c:26:
/usr/src/contrib/gcc/obstack.h:157:40: attempt to use poisoned "bcopy"
c-parse.y:34:20: config.h: No such file or directory
In file included from c-parse.y:35:
/usr/src/contrib/gcc/system.h:110:24: safe-ctype.h: No such file or directory
In file included from c-parse.y:36:
/usr/src/contrib/gcc/tree.h:332:24: tree-check.h: No such file or directory
In file included from /usr/src/contrib/gcc/hashtable.h:21,
                 from /usr/src/contrib/gcc/tree.h:775,
                 from c-parse.y:36:
/usr/src/contrib/gcc/obstack.h:157:40: attempt to use poisoned "bcopy"
/usr/src/contrib/gcc/c-lang.c:23:20: config.h: No such file or directory
In file included from /usr/src/contrib/gcc/c-lang.c:24:
/usr/src/contrib/gcc/system.h:110:24: safe-ctype.h: No such file or directory
[...]

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED]         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to