From: Benjamin Kosnik <bkoz@redhat.com>
To: janis187@us.ibm.com
Cc: gcc@gcc.gnu.org
Subject: Re: libstdc++ testsuite failures and GLIBCPP_BUILD_PCH
Date: Wed, 23 Apr 2003 19:25:00 -0000 [thread overview]
Message-ID: <20030423140317.6a008c7a.bkoz@redhat.com> (raw)
> So, what magic is going on with @GLIBCPP_BUILD_PCH_TRUE@ and
> @GLIBCPP_BUILD_PCH_FALSE@, and why are they both true for my cross
> build?
Hmm.
at libstdc++-v3/configure.in: 406
GLIBCPP_CHECK_COMPILER_FEATURES
GLIBCPP_CHECK_PCH
Where GLIBCPP_CHECK_PCH is a macro defined in acinclude.m4 to test if
PCH can be used. This macro is only called in the native case, which
actually is overly-conservative now that I think about it.
Since it doesn't do linking, this might as well get moved up, to line 55.
If you want to do this, and make sure it works for you, patch pre-approved.
-benjamin
next reply other threads:[~2003-04-23 19:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 19:25 Benjamin Kosnik [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-23 18:50 Janis Johnson
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=20030423140317.6a008c7a.bkoz@redhat.com \
--to=bkoz@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=janis187@us.ibm.com \
/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).