From owner-freebsd-current Fri Mar 8 12:23:44 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id 7242A37B416; Fri, 8 Mar 2002 12:23:26 -0800 (PST) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.12.1/8.12.1) with ESMTP id g28KNONH084208; Fri, 8 Mar 2002 15:23:24 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20020309044402.P4157-100000@gamplex.bde.org> References: <20020309044402.P4157-100000@gamplex.bde.org> Date: Fri, 8 Mar 2002 15:23:23 -0500 To: Bruce Evans , "David W. Chapman Jr." From: Garance A Drosihn Subject: Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Cc: Robert Watson , Murray Stokely , , , , Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.3 (www dot roaringpenguin dot com slash mimedefang) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 4:57 AM +1100 3/9/02, Bruce Evans wrote: >I'm surprised that everyone hasn't complained about world breakage >from this. It has been broken for almost 2 weeks now. Everything >that goes near ntohl and has WARNS >= 2 fails to compile. Without >WARNS, the bug is reported as above, but a bogus version of __hton* >is found in the library and only optimization of hton* is broken. Well, I get compile-time warning messages when doing a buildworld of current, but nothing actually breaks. I do not do much of anything fancy with resetting WARNS, so my guess is that the "default buildworld settings" will not run into a show-stopping error due to these loose ends. I think part of it is that some things (like 'lpr' for instance) were changed to use 'BDECFLAGS' instead of some compiler-specific list of flags (in -stable lpr has '-Wall -Wnested-externs -Wmissing-prototypes -Wno-unused -Wredundant-decls -Wstrict-prototypes'). That probably sounds like a step up in warning level, except that we also removed BDECFLAGS from /etc/defaults/make.conf. In fact, there is no /etc/defaults/make.conf in current, it was moved to /usr/share/examples/etc/make.conf. So I expect that most people (including me) have effectively gone to compiling with zero special CWARNFLAGS parameters for those modules. I'll make a wild guess and say that it's possible that Bruce might have some BDECFLAGS set in his /etc/make.conf, so he is probably seeing more warning messages than the average person... -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message