Date: Wed, 10 Jul 2002 14:22:12 -0700 (PDT) From: Matthew Dillon <dillon@apollo.backplane.com> To: Dag-Erling Smorgrav <des@ofug.org> Cc: Giorgos Keramidas <keramida@FreeBSD.ORG>, current@FreeBSD.ORG Subject: Re: sparc64 tinderbox failure Message-ID: <200207102122.g6ALMCi1004528@apollo.backplane.com> References: <200207100958.g6A9wFmY072199@bowie.private> <20020710172346.GB1118@hades.hell.gr> <xzpadoznvcv.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
:
: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.
:
:DES
:--
:Dag-Erling Smorgrav - des@ofug.org
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. I'm going to finish what I've been doing and if someone has a
real huge chip on their shoulder and can't handle the strain then they
can fix __printf0like and then back-out some or all of my changes with
my permission.
Personally speaking, as much as GCC annoys me it is sometimes better to
modify the utility code then to add yet another hack to GCC that needs
to be synchronized every time we update.
-Matt
Matthew Dillon
<dillon@backplane.com>
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?200207102122.g6ALMCi1004528>