From owner-freebsd-hackers Fri Apr 21 16:57:32 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA25235 for hackers-outgoing; Fri, 21 Apr 1995 16:57:32 -0700 Received: from wdl1.wdl.loral.com (wdl1.wdl.loral.com [137.249.32.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id QAA25228 for ; Fri, 21 Apr 1995 16:57:29 -0700 Received: from miles.sso.loral.com by wdl1.wdl.loral.com (4.1/WDL-4.2) id AA16657; Fri, 21 Apr 95 16:56:55 PDT Received: by miles.sso.loral.com (4.1/SSO-SUN-2.04) id AA19477; Fri, 21 Apr 95 19:57:52 EDT Date: Fri, 21 Apr 1995 19:57:50 -0400 (EDT) From: Richard Toren X-Sender: rpt@miles To: hackers@FreeBSD.org Subject: _ANSI_SOURCE... who defines this puppy Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hackers-owner@FreeBSD.org Precedence: bulk I am trying to get pthreads to build on 2.0R. I have had a number of problems, but this last one led me down a rat hole that seems to go beyond pthreads. In one source file was : #if !defined(_ANSI_SOURCE) #define CLK_TCK 100 #endif /* not ANSI */ This resulted in redefinition of the value in . So I started to try to hunt down who defines _ANSI_SOURCE. I found it referenced numerous times in places in the standard includes. But I can't find anywhere that it is defined. The best gcc does is: <~/code>> cc -E -dM -ansi foo.c #define __STRICT_ANSI__ 1 #define __FreeBSD__ 2 #define __i386__ 1 #define __i386 1 #define __GNUC_MINOR__ 6 #define __unix 1 #define __unix__ 1 #define __GNUC__ 2 So is this the programmers responsibility to define? ==================================================== Rip Toren | The bad news is that C++ is not an object-oriented | rpt@miles.sso.loral.com | programming language. .... The good news is that | | C++ supports object-oriented programming. | | C++ Programming & Fundamental Concepts | | by Anderson & Heinze | ====================================================