From owner-freebsd-current  Fri Sep 18 23:05:07 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id XAA26527
          for freebsd-current-outgoing; Fri, 18 Sep 1998 23:05:07 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA26520
          for <current@freebsd.org>; Fri, 18 Sep 1998 23:05:03 -0700 (PDT)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id QAA01497;
	Sat, 19 Sep 1998 16:04:36 +1000
Date: Sat, 19 Sep 1998 16:04:36 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199809190604.QAA01497@godzilla.zeta.org.au>
To: bde@zeta.org.au, jdp@polstra.com
Subject: Re: __ELF__ and the likes
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>> >Are there plans for implementing __ELF__ as a cpp define?
>> 
>> I hope not.
>
>I'm curious about this.  I've always felt that cpp should do exactly
>the same thing as "cc -E".  Why is it that we don't do that?

cpp gets (ab)used for things not related to compiling C programs with cc.
It should not depend on what today's version of cc does.  /usr/bin/cpp
does something closer to
"cc -E -P -traditional -D__GNUC__ -$ -nostdinc -I/usr/include"
to keep close to what old versions of cc did (defining __GNUC__ and
modifying the include search path here are wrong).

Bruc

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message