From owner-freebsd-bugs Tue Jul 9 14:30: 9 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E91337B400 for ; Tue, 9 Jul 2002 14:30:05 -0700 (PDT) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 313FB43E09 for ; Tue, 9 Jul 2002 14:30:05 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.4/8.12.4) with ESMTP id g69LU4JU092809 for ; Tue, 9 Jul 2002 14:30:04 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.4/8.12.4/Submit) id g69LU4tk092808; Tue, 9 Jul 2002 14:30:04 -0700 (PDT) Date: Tue, 9 Jul 2002 14:30:04 -0700 (PDT) Message-Id: <200207092130.g69LU4tk092808@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Bruce Evans Subject: Re: misc/40378: stdlib.h gives needless warnings with -ansi Reply-To: Bruce Evans Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR misc/40378; it has been noted by GNATS. From: Bruce Evans To: Dimitry Andric Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: misc/40378: stdlib.h gives needless warnings with -ansi Date: Wed, 10 Jul 2002 07:24:08 +1000 (EST) On Tue, 9 Jul 2002, Dimitry Andric wrote: > >Description: > Since my latest cvsup (from 4.6-RC to 4.6-STABLE), lots of programs > that are built with the gcc `-ansi' option have started complaining > about stdlib.h, like this: > > In file included from ../../../../../../extras/Mesa/src/glheader.h:60, > from ../../../../../../extras/Mesa/src/types.h:32, > from mgafastpath.c:31: > /usr/include/stdlib.h:108: warning: ANSI C does not support `long long' > /usr/include/stdlib.h:112: warning: ANSI C does not support `long long' > > It seems that there has been some fiddling with __LONG_LONG_SUPPORTED > and related defines, and these two functions have been missed, maybe? RELENG_4 was broken here between 4.2-RELEASE and 4.3-RELEASE. The "fiddling" to fix the problem is only in -current. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message