On Mon, 3 Jul 2000, Mo DeJong wrote:
> > My concern is, on some platforms gcc -pipe just silently fails to create
> > an output file but does not return an error code.
>
> That sounds like the sort of "feature test" that autoconf
> should be doing to make sure -pipe can be used. Could
> you write up a macro to detect this case? You should
> also submit a gcc bug report on this problem.
The problem was mentioned on the Cygwin mailing list
(http://sourceware.cygnus.com/ml/cygwin/1998-02/msg00658.html) and a look
into the GCC mailing lists indicates that a patch has been submitted at
the end of 1998. (http://gcc.gnu.org/ml/gcc-patches/1998-12/msg00482.html)
But it may affect any system with non-standard pipe semantics.
I'm also concerned about the simplistic "add -pipe to CFLAGS and try a
compile" approach because GCC doesn't reject unknown arguments
consistently. (Try -pipex.) It seems the least we'd need to do is to check
for an output file and check for an empty stderr. (Better yet, check for
an output file that is sufficiently similar to the non-pipe case. But
that's magnitudes harder.)
--
Peter Eisentraut Sernanders vaeg 10:115
[EMAIL PROTECTED] 75262 Uppsala
http://yi.org/peter-e/ Sweden
