The usage came about oh about 8 years ago with the very first port
of X to 386bsd by yours truly 8)

Don't forget I did fix the problem on my X build and I am running
the latest XFree86 3.9.xx on my other box.

        Take Care

> > 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    ([EMAIL PROTECTED])

-- 

 Amancio Hasty
 [EMAIL PROTECTED]




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to