From: Pat <spamok@yahoo.com>
To: gcc-help@gcc.gnu.org
Subject: pch doesn't seem to be used
Date: Sun, 05 Sep 2004 22:33:00 -0000 [thread overview]
Message-ID: <413B967D.8050600@yahoo.com> (raw)
Hi,
I have a Precomp.h header, in which the most used headers are #included,
and, in the same directory, the compiled Precomp.h.gch
At the start of the compilation, the pch is read and verified correctly
because when the options used to compile it are changed, the correct
warning appears.( "warning: ./Precomp.h.gch: created with different flags" )
Immediately after that, the gch file is closed and the compiler starts
to read the original headers files.
Any hint ?
Pat
next reply other threads:[~2004-09-05 22:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-05 22:33 Pat [this message]
2004-09-07 12:31 ` Eljay Love-Jensen
2004-09-07 18:47 Pat
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=413B967D.8050600@yahoo.com \
--to=spamok@yahoo.com \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).