This is the mail archive of the
mailing list for the GCC project.
Re: unrecognized option '-no-cpp-precomp' on Mac OS X (10.4.3)
- From: Daniel Jacobowitz <drow at false dot org>
- To: Paul Martinolich <martinol at nrlssc dot navy dot mil>
- Cc: gcc at gcc dot gnu dot org
- Date: Wed, 14 Dec 2005 15:54:57 -0500
- Subject: Re: unrecognized option '-no-cpp-precomp' on Mac OS X (10.4.3)
- References: <EDCF4A92-39CD-4DD3-92BF-3FBB34414E62@nrlssc.navy.mil>
On Wed, Dec 14, 2005 at 02:52:26PM -0600, Paul Martinolich wrote:
> I have built gcc-4.1-20051209 successfully and while using it to try to
> compile Python-2.4.2, I get this error:
> /Users/martinol/auto_v4.0/devel/powerpc-apple-darwin8.3.0/bin/gcc -c -
> fno-strict-aliasing -Wno-long-double -no-cpp-precomp -mno-fused-madd -
> DNDEBUG -g -O3 -Wall -Wstrict-prototypes -I. -I/Users/martinol/build-
> magnesium/Python-2.4.2/Include -DPy_BUILD_CORE -o Modules/python.o /
> gcc: unrecognized option '-no-cpp-precomp'
> cc1: error: unrecognized command line option "-Wno-long-double"
> make: *** [Modules/python.o] Error 1
> make: *** [python-build] Error 2
> Using grep, I see stage1 flags that use this option. However, the on-
> line documentation did not
> seem to have this option in it -- at least not in the section dealing
> with command line options
> for the CPP.
> Any ideas where it might have gone? Is it an "internal" option?
It is only supported by Apple's compiler, not part of the FSF GCC.
Python is incorrect for using it unconditionally based on the target.