From owner-freebsd-hackers Thu Feb 1 12:33:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id 3B6C237B4EC for ; Thu, 1 Feb 2001 12:33:36 -0800 (PST) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id f11KWcl06065; Thu, 1 Feb 2001 12:32:38 -0800 (PST) Date: Thu, 1 Feb 2001 12:32:37 -0800 (PST) From: Doug White To: Alex Kapranoff Cc: hackers@FreeBSD.ORG Subject: Re: FreeBSD specific strftime(3) format specifiers In-Reply-To: <20010128102544.A2192@kapran.bitmcnit.bryansk.su> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 28 Jan 2001, Alex Kapranoff wrote: > Hi to all. > gcc supports strftime format string checking and issues a warning when > it encounters some unknown format specifier. FreeBSD strftime has > several additional format chars which gcc knows nothing about. > > This can easily be seen when compiling /usr/src/usr.sbin/pw: > pw_user.c:1175: warning: unknown conversion type character `f' in format > pw_user.c:1177: warning: unknown conversion type character `f' in format > > Are there chances that this could be fixed? I suppose, the patches > should be submitted to gcc developers and the changes will get into > our tree on next gcc source import? I believe there is a -fformat-extensions flag that gets around this problem. Check out the kernel build for the actual flag as it's used there. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message