From owner-freebsd-current Wed Dec 29 16:53:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id D371915105; Wed, 29 Dec 1999 16:53:49 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA03485; Wed, 29 Dec 1999 16:58:23 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912300058.QAA03485@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Amancio Hasty Cc: Mike Smith , current@freebsd.org Subject: Re: gcc compiler problem part deux In-reply-to: Your message of "Wed, 29 Dec 1999 16:48:59 PST." <199912300048.QAA45447@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Dec 1999 16:58:23 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > There are packages such as XFree86 which called directly the installed > cpp. Those packages which rely on the old behavior of /usr/libexec/cpp > for instance defining __FreeBSD__ are now broken . XFree86 is trivial to patch, since it already supports this behaviour (see our port), and other applications that expect cpp to define platform-specific symbols have always been broken. > > This was discussed weeks ago, and the new behaviour is correct. You > > should be using 'cc -E' instead. > > > > > > > > Forgot to post about this new feature of /usr/libexec/cpp : -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message