Date: Thu, 11 Jul 2002 00:29:42 +0300 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: Dag-Erling Smorgrav <des@ofug.org>, current@FreeBSD.ORG Subject: Re: sparc64 tinderbox failure Message-ID: <20020710212942.GC4189@hades.hell.gr> In-Reply-To: <200207102122.g6ALMCi1004528@apollo.backplane.com> References: <200207100958.g6A9wFmY072199@bowie.private> <20020710172346.GB1118@hades.hell.gr> <xzpadoznvcv.fsf@flood.ping.uio.no> <200207102122.g6ALMCi1004528@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2002-07-10 14:22 +0000, Matthew Dillon wrote: > :Giorgos Keramidas <keramida@FreeBSD.org> writes: > :> How does this look for fixing this warning? > : > :No, gcc should accept a NULL format string for err(3). It looks like > :__printf0like is broken. > > Oops. I've already starting changing the calls to err(). I would > really like buildworld to work and there aren't too many of them, and > besides a little more verboseness for some of these failures is not a bad > thing. The extra verboseness is fine, and I was almost finished posting a note that mentioned it. But I didn't thinking that the __printf0like bugs will never be fixed if we hide them by patching chmod. Nevertheless, I do agree that a more verbose error message is likely to be an improvement in this particular case. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020710212942.GC4189>