Date: Wed, 29 Dec 1999 17:04:12 -0800 From: Amancio Hasty <hasty@rah.star-gate.com> To: Mike Smith <msmith@freebsd.org> Cc: current@freebsd.org Subject: Re: gcc compiler problem part deux Message-ID: <199912300104.RAA45566@rah.star-gate.com> In-Reply-To: Your message of "Wed, 29 Dec 1999 16:58:23 PST." <199912300058.QAA03485@mass.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
It is more of a question of whether the packages for FreeBSD expect /usr/libexec/cpp to define __FreeBSD__ and in my case XFree86. Once I managed to find out what was wrong it was indeed easy for me to fix. If the "other" applications managed to compile correctly on FreeBSD because of /usr/libexec/cpp then I don't consider them to be broken. > > 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 > > -- Amancio Hasty hasty@rah.star-gate.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?199912300104.RAA45566>