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, \\ [EMAIL PROTECTED]
> \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED]
>
>
--
Amancio Hasty
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
