Re: anyone else having trouble compiling libc in i386-current?

[Kurt Schreiner <ks%ub.uni-mainz.de@localhost>]

Hi,

On Sun, Aug 24, 2008 at 09:11:41AM +0200, Tobias Nygren wrote:
> On Sat, 23 Aug 2008 23:43:34 -0700 (PDT)
> Hisashi T Fujinaka <htodd%twofifty.com@localhost> wrote:
> 
> > #   compile  libc/fixunsdfdi.ln
> > /usr/src/lib/libc/quad/fixunsdfdi.c(64): warning: integer constant out of 
> > range [252]
> > /usr/src/lib/libc/quad/fixunsdfdi.c(70): warning: integer constant out of 
> > range [252]
> 
> Happens here as well. Building with MKLINT=no seems to get past that.
> 
<aol> Me too </aol> ;-)
see http://mail-index.netbsd.org/current-users/2008/08/22/msg004093.html

I use the following patch in my local tree:

>-1034: cvs diff -u Makefile.inc 
Index: Makefile.inc
===================================================================
RCS file: /cvsroot/src/lib/libc/Makefile.inc,v
retrieving revision 1.3
diff -u -r1.3 Makefile.inc
--- Makefile.inc        3 Jun 2007 17:36:08 -0000       1.3
+++ Makefile.inc        24 Aug 2008 13:03:04 -0000
@@ -46,6 +46,8 @@
 LINTFLAGS+=    -w
 .endif
 # ignore 'empty translation unit' warnings.
 LINTFLAGS+=    -X 272
+# ignore 'integer constant out of range' warnings, too.
+LINTFLAGS+=    -X 252
 
 .if exists(${.CURDIR}/arch/${MACHINE_ARCH})
 ARCHSUBDIR=    ${MACHINE_ARCH}

Not a real fix, I suppose, but lint is quiet now...

Kurt