Date: Thu, 30 Dec 1999 17:57:24 -0800 (PST) From: John Polstra <jdp@polstra.com> To: peter.jeremy@ALCATEL.COM.AU Cc: current@freebsd.org Subject: Re: gcc compiler problem part deux Message-ID: <199912310157.RAA39464@vashon.polstra.com> In-Reply-To: <99Dec31.091308est.40324@border.alcanet.com.au> References: <99Dec31.091308est.40324@border.alcanet.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <99Dec31.091308est.40324@border.alcanet.com.au>, Peter
Jeremy <peter.jeremy@ALCATEL.COM.AU> wrote:
> Last time I checked (I haven't moved to the latest gcc, so I can't
> confirm it there), one significant difference between 'cc -E'
> and /usr/libexec/cpp was that the latter would read from a pipe,
> whilst the former wouldn't. This can make converting to 'cc -E' a
> non-trivial exercise.
That's what /dev/stdin is for:
cat hello.c | cc -E -x c /dev/stdin
John
--
John Polstra jdp@polstra.com
John D. Polstra & Co., Inc. Seattle, Washington USA
"Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa
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?199912310157.RAA39464>