From: Janis Johnson <janis187@us.ibm.com>
To: gcc@gcc.gnu.org
Subject: libstdc++ testsuite failures and GLIBCPP_BUILD_PCH
Date: Wed, 23 Apr 2003 18:50:00 -0000 [thread overview]
Message-ID: <20030423111917.A13536@us.ibm.com> (raw)
Testing of libstdc++-v3 for a cross powerpc64-linux compiler fails
because bits/stdc++.h isn't found. It appears to be a configuration
or build problem, but I don't understand how that mechanism works.
From libstdc++-v3/include/Makefile.am:
if GLIBCPP_BUILD_PCH
pch_build = ${pch_input}
pch_install = install-pch
else
pch_build =
pch_install =
endif
From libstdc++-v3/include/Makefile.in:
@GLIBCPP_BUILD_PCH_TRUE@pch_build = ${pch_input}
@GLIBCPP_BUILD_PCH_FALSE@pch_build =
@GLIBCPP_BUILD_PCH_TRUE@pch_install = install-pch
@GLIBCPP_BUILD_PCH_FALSE@pch_install =
For a native i686-linux build, from
i686-pc-linux-gnu/libstdc++-v3/include/Makefile:
pch_build = ${pch_input}
#pch_build =
pch_install = install-pch
#pch_install =
For a cross build of powerpc64-linux from powerpc-linux, from
powerpc64-linux/libstdc++-v3/include/Makefile:
pch_build = ${pch_input}
pch_build =
pch_install = install-pch
pch_install =
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?
Janis
next reply other threads:[~2003-04-23 18:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 18:50 Janis Johnson [this message]
2003-04-23 19:25 Benjamin Kosnik
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=20030423111917.A13536@us.ibm.com \
--to=janis187@us.ibm.com \
--cc=gcc@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).