public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/107134] fatal error: stdint.h: No such file or directory for freestanding C++ toolchain
Date: Mon, 03 Oct 2022 19:40:44 +0000 [thread overview]
Message-ID: <bug-107134-4-qLQcrUfPlw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107134-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107134
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to cqwrteur from comment #0)
> x86_64-elf-g++ -c b.cc -std=c++23
> In file included from
> /home/cqwrteur/toolchains/native/x86_64-elf/x86_64-elf/include/c++/13.0.0/
> cstdint:41,
> from b.cc:1:
> /home/cqwrteur/toolchains/native/x86_64-elf/lib/gcc/x86_64-elf/13.0.0/
> include/stdint.h:9:16: fatal error: stdint.h: No such file or directory
Wait a minute, why do you even have libstdc++'s <stdint.h> installed for this
configuration?
next prev parent reply other threads:[~2022-10-03 19:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 17:31 [Bug c++/107134] New: " unlvsur at live dot com
2022-10-03 17:36 ` [Bug c++/107134] " redi at gcc dot gnu.org
2022-10-03 18:06 ` redi at gcc dot gnu.org
2022-10-03 19:40 ` redi at gcc dot gnu.org [this message]
2022-10-03 19:42 ` redi at gcc dot gnu.org
2022-10-03 20:57 ` redi at gcc dot gnu.org
2022-10-04 14:07 ` cvs-commit at gcc dot gnu.org
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=bug-107134-4-qLQcrUfPlw@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).