Subject: Re: problem building distribution
To: Martin Husemann <martin@duskware.de>
From: Adam Bozanich <abozan01@ccsf.edu>
List: port-sparc64
Date: 11/25/2003 16:45:42
On Wed, 26 Nov 2003, Martin Husemann wrote:

> It is not supposed to install anything. You (or build.sh) are supposed to
> run the new tools from the tooldir. So you would do something like
>
>   /usr/tools/bin/nbconfig GENERIC
>   /usr/tools/bin/nbmake-sparc64 depend
>   /usr/tools/bin/nbmake-sparc64
>
> or: just use "build.sh kernel=GENERIC"

I had tried this, but It bailed out on me.

> Did you boot the new kernel in between but not explicitly specify a tooldir
> (via setting $TOOLDIR in the environment or by passing -T to build.sh)?

Yes, I did boot the new kernel, and I did not specify a tooldir.

>
> This may have confused build.sh (but usually it would deal with this).
> I guess it has build the tools in your objdir with a name including the
> kernel version running at the first "build.sh tools" and now looks for them
> at a similar path with the new version number. There is magic in build.sh
> to figure this out, but it might have failed in your case.
>
> > In file included from /usr/src/gnu/dist/gcc/gcc/gengenrtl.c:29:
> > /usr/src/gnu/dist/gcc/gcc/real.h:67: size of array `test_real_width' is negative
>
> I have never seen this, though I'm not sure how well tested the compiler
> bootstrap from the old, crappy gcc in 1.6.x is.
>
> Martin
>

I'd love to try out some of your suggestions <and read some more of
src/BUILDING> , but now I am having problems w/ my filesystem.

/dev/rwd0e:  BAD SUPER BLOCK: VALUSE IN SUPER BLOCK DISAGREE WITH THOSE IN
FIRST ALTERNATE
/dev/rwd0e: UNEXPECTED INCONSISTENCY; RUN fsck_ffs manually.

so it drops me to a shell....

#/sbin/fsck_ffs -y /dev/rwd0e
BAD SUPER BLOCK: VALUSE IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST
ALTERNATE
Floating point exception

The odd thing is that I can use fsck on any other partion, but I get this
floating point exception on rwd0e only (my /home partition)

I tried this booting both my kernel and the GENERIC kernel.

Any suggestions?

-Adam Bozanich