Date: Wed, 10 Jul 2002 22:10:09 -0400 From: Garance A Drosihn <drosih@rpi.edu> To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org, Matthew Dillon <dillon@apollo.backplane.com> Cc: Dag-Erling Smorgrav <des@ofug.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/bin/chmod chmod.c Message-ID: <p0511174ab952963a6573@[128.113.24.47]> In-Reply-To: <20020711002222.GA27696@dragon.nuxi.com> References: <200207102036.g6AKaQej039281@freefall.freebsd.org> <xzpn0szmfrx.fsf@flood.ping.uio.no> <200207102133.g6ALXqu2016453@apollo.backplane.com> <xzpelebmfg1.fsf@flood.ping.uio.no> <200207102141.g6ALfF8w029851@apollo.backplane.com> <xzpadozmex6.fsf@flood.ping.uio.no> <200207102215.g6AMFDJ9075934@apollo.backplane.com> <20020711002222.GA27696@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 5:22 PM -0700 7/10/02, David O'Brien wrote: >On Wed, Jul 10, 2002 at 03:15:13PM -0700, Matthew Dillon wrote: >> (1) abandon __printf0like for err(), warn(), and errx(). >> or >> (2) hack GCC to make it allow NULLs for __printf0like. >> or >> (3) apply the patch below. > >or import GCC 3.2 which knows about __printf0like natively. If we know that the next version of GCC will deal with these NULL's for __printf0like, then I would rather not go with the patches that Matt proposed. -- Garance Alistair Drosehn = gad@gilead.netel.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 cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p0511174ab952963a6573>