matthew green wrote:
> that looks like you have a badly updated tree.  this should be fixed
> since a few days ago...  make sure your obj-tree "options.h" is cleared
> out i guess.  it used to be empty and now is not.. it is where the
> ppc TARGET_ALTIVEC is defined.
>
> PR's are fine for GCC4.  or here... :-)
>
>
> .mrg.
>   


Hi again,

Its not that simple.

I just wiped all of src/gnu/dist/gcc4 and src/gnu/usr.bin/gcc4 and then
did a fresh cvs -z3 -q update -dP -- or rather did the update
twice to observe that there were no local changes except for a gross
hack that I had to make in oea_machdep.c in order to make the kernel
compile.

I also wiped all of obj.macppc before rebuilding.

Also a complete sh build tools kernel=HJEMME did complete before
running into problems (and the machine is running on the gcc4
generated kernel).

However, I notice that on my failing macppc I have

g find . -name options.h | xargs ls -l
-rw-r--r--  1 root  wheel      0 Jun  1 12:54 ./gnu/lib/crtstuff4/options.h
-rw-r--r--  1 root  wheel      0 Jun  1 12:54 
./gnu/lib/libgcc4/libgcc/options.h
-rw-r--r--  1 root  wheel      0 Jun  1 12:57 
./gnu/lib/libgcc4/libgcc_eh/options.h
-rw-r--r--  1 root  wheel      0 Jun  1 12:57 
./gnu/lib/libgcc4/libgcc_s/options.h
-rw-r--r--  1 root  wheel  48248 Jun  1 11:02 
./tools/gcc/build/gcc/options.h
g pwd
/home/NetBSD/obj.macppc
g


while on a succeding i386 I have

medja find . -name options.h | xargs ls -l
-rw-r--r--  1 root  wheel      0 May 22 07:45 ./gnu/lib/crtstuff4/options.h
-rw-r--r--  1 root  wheel      0 May 22 07:45 
./gnu/lib/libgcc4/libgcc/options.h
-rw-r--r--  1 root  wheel      0 May 22 07:45 
./gnu/lib/libgcc4/libgcc_eh/options.h
-rw-r--r--  1 root  wheel      0 May 22 07:45 
./gnu/lib/libgcc4/libgcc_s/options.h
-rw-r--r--  1 root  wheel  46456 May 26 08:52 ./gnu/lib/libobjc4/options.h
-rw-r--r--  1 root  wheel  46456 May 22 08:20 
./gnu/usr.bin/gcc4/backend/options.h
-rw-r--r--  1 root  wheel  46456 May 21 20:32 
./tools/gcc/build/gcc/options.h
medja pwd
/home/NetBSD/obj.i386
medja

I do admit that I was doing a

    sh build.sh -u -E build

after rebooting.

I'll now rerun the build.sh with an explicit destdir and see if that makes
any difference.

- Erik