public inbox for
help / color / mirror / Atom feed
From: Dara Hazeghi <>
Subject: Re: other/10777: gcc: unrecognized option `-no-cpp-precomp'
Date: Wed, 14 May 2003 07:36:00 -0000	[thread overview]
Message-ID: <> (raw)

The following reply was made to PR other/10777; it has been noted by GNATS.

From: Dara Hazeghi <>
Subject: Re: other/10777: gcc: unrecognized option `-no-cpp-precomp'
Date: Wed, 14 May 2003 00:34:02 -0700 
 first, before you e-mail the gcc release manager, you should at least  
 send a message to Mark is responsible for seeing  
 that the releases get out, not for all the problems in gcc. That's why  
 we have a bugs mailing list.
 Second, the reason for this behavior is fairly simple. Apple's gcc has  
 something called cpp-precomp which was their old method of precompiled  
 headers. Official gcc releases don't have this option (it is an Apple  
 specific thing, and will be going away soon, since it's now obsolete).
 We disable it when building gcc because it has a number of bugs which  
 may cause compilation to fail. Because 99% of the people building gcc  
 on MacOS X will be building it with Apple's gcc, we need to disable  
 cpp-precomp to prevent the builds from failing.
 Unfortunately, as seen in your case, because we assume Apple gcc is the  
 compiler being used to build gcc on MacOS X, we assume this option to  
 disable cpp-precomp is available. In your case, to get rid of the  
 warnings, all you have to do is set the CFLAGS environment variable to  
 -O2 -g, ie do setenv CFLAGS "-O2 -g"  before building gcc, and this  
 warning should go away. Hopefully we can come up with a way to automate  
 this in the future.

             reply	other threads:[~2003-05-14  7:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-14  7:36 Dara Hazeghi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-14 14:10 bangerth
2003-05-14 12:06 Andrew Pinski
2003-05-14  6:36 shrao

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).