From owner-freebsd-current  Sat Jan  1 15:54:34 2000
Delivered-To: freebsd-current@freebsd.org
Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10])
	by hub.freebsd.org (Postfix) with ESMTP id ED75D14FB9
	for <current@FreeBSD.ORG>; Sat,  1 Jan 2000 15:54:29 -0800 (PST)
	(envelope-from jeremyp@gsmx07.alcatel.com.au)
Received: by border.alcanet.com.au id <40326>; Sun, 2 Jan 2000 10:47:29 +1100
Content-return: prohibited
From: Peter Jeremy <peter.jeremy@alcatel.com.au>
Subject: Re: gcc compiler problem part deux
To: current@FreeBSD.ORG
Message-Id: <00Jan2.104729est.40326@border.alcanet.com.au>
MIME-version: 1.0
X-Mailer: Mutt 1.0i
Content-type: text/plain; charset=us-ascii
Date: Sun, 2 Jan 2000 10:47:24 +1100
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I 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.

It seems I was wrong.  As several people have pointed out, both
'cc -E -' and 'cc -x c -E /dev/stdin' work.  I'll crawl back into
the woodwork for a while :-).

Peter


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message