Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 22 Apr 2003 21:34:13 -0500
From:      David Leimbach <leimy2k@mac.com>
To:        freebsd-current@freebsd.org
Cc:        Poul-Henning Kamp <phk@critter.freebsd.dk>
Subject:   Makefile in /usr/src/lib/libdisk WARNS change? PLEASE READ!
Message-ID:  <11FEE921-7534-11D7-A805-0003937E39E0@mac.com>

next in thread | raw e-mail | index | archive | help
Hi,

I posted the libdisk patch that was heavily ignored two days ago :).  
Without it I
couldn't build libdisk and subsequently world.  If I lower the WARNS 
value
in the libdisk directory Makefiel the source builds without warning and 
world
completes.

The problem is rules.c having a switch/case that handles only 2 of 7 
cases for the
platform value.  Adding a simple "default:" [as my patch did] will 
repair this problem.

I should tell you that I clean-installed FBSD 5.0-RELEASE on Saturday 
4/19/2003
and started playing with CURRENT again the very next day at which point 
I realized
world wouldn't build.  I didn't do much else so I can only assume that 
somehow this
could happen to anyone else starting from RELEASE-5 today and 
attempting to build
world.

I have the latest version of the rules.c file [1.29]. I checked CVSWEB 
and it has
the exact same code that fails for me in HEAD so I know its not my 
source.  The
only data involved in the switch is an enum type from libdisk.h which I 
also
have the latest version of [1.55].

The error is
/usr/src/lib/libdisk/rules.c:264: warning: enumeration value `p_any' 
not handled in switch
/usr/src/lib/libdisk/rules.c:264: warning: enumeration value `p_alpha' 
not handled in switch
/usr/src/lib/libdisk/rules.c:264: warning: enumeration value 
`p_sparc64' not handled in switch
/usr/src/lib/libdisk/rules.c:264: warning: enumeration value `p_ia64' 
not handled in switch
/usr/src/lib/libdisk/rules.c:264: warning: enumeration value `p_ppc' 
not handled in switch
*** Error code 1.

I know this isn't a bug in the VM system.  Its not solving a kernel 
panic or
some other serious commit but it does pose a barrier to those who want 
to test CURRENT.

Should I file a problem report?

Dave Leimbach



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?11FEE921-7534-11D7-A805-0003937E39E0>