Date: Wed, 29 Dec 1999 18:49:01 -0800 From: "David O'Brien" <obrien@freebsd.org> To: Amancio Hasty <hasty@rah.star-gate.com> Cc: current@freebsd.org Subject: Re: gcc compiler problem part deux Message-ID: <19991229184901.A16090@dragon.nuxi.com> In-Reply-To: <199912300022.QAA45237@rah.star-gate.com>; from hasty@rah.star-gate.com on Wed, Dec 29, 1999 at 04:22:28PM -0800 References: <199912300022.QAA45237@rah.star-gate.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Forgot to post about this new feature of /usr/libexec/cpp : NO ONE should have ever have been using /usr/libexec/cpp directly. I have no idea where this usage came from. /usr/bin/cpp should have been used. > 2. Now a very recent FreeBSD -current > gcc -v > Using builtin specs. > gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release) Yes this is very well known, and has been discussed on both Ports and Current several times. A new /usr/bin/ccp is in the works that is a real binary and not the shell script we have today. *IF* world had been buildable today, we would probably have a new /usr/bin/cpp that does everything you want it to. > This behavior breaks the XFree86 3.9.17 build because the procedure > to build imake depends on /usr/libexec/cpp defining __FreeBSD__ So use ``cc -E'' instead. Simple. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991229184901.A16090>