From: "Anton Wöllert" <a.woellert@gmail.com>
To: gcc@gcc.gnu.org
Subject: Relation between gcc version and libstdc++ version
Date: Tue, 30 Aug 2022 16:47:14 +0200 [thread overview]
Message-ID: <4161b707473552ce74c41c8867c2cc6d77ff4e05.camel@gmail.com> (raw)
Hello list!
I was trying to build a cross-compilation toolchain for a specific
target using a newer GCC version, than the one that the binaries were
build on the target.
The C part seems to work well, but the C++ part doesn't. It seems that
the G++ ships it's own libstdc++ include headers. If this libstdc++ is
newer than the one one the target, I get undefined references (because
there are some newer implementation details and things like that). Is
it possible to tell G++/GCC to use the libstdc++.so from the target and
also to use the C++ headers (like iostream) from the target?
If not, is there any reason this is hard-coded?
With clang it looks like you can specify "any" libstdc++ version you
want, although I haven't tested it yet.
Kind regards,
Anton
next reply other threads:[~2022-08-30 14:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 14:47 Anton Wöllert [this message]
2022-08-30 16:09 ` Jonathan Wakely
2022-08-30 16:09 ` Jonathan Wakely
2022-08-30 16:53 ` Anton Wöllert
2022-08-30 17:20 ` Jonathan Wakely
2022-08-30 17:20 ` Jonathan Wakely
2022-08-30 17:21 ` Jonathan Wakely
2022-08-30 17:21 ` Jonathan Wakely
2022-08-30 18:46 ` Anton Wöllert
2022-08-30 19:24 ` Jonathan Wakely
2022-08-30 19:24 ` Jonathan Wakely
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=4161b707473552ce74c41c8867c2cc6d77ff4e05.camel@gmail.com \
--to=a.woellert@gmail.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).