public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "unlvsur at live dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/104157] New: libc++ does not work properly with x86_64-w64-mingw32 host, but works fine with x86_64-linux-gnu host
Date: Fri, 21 Jan 2022 05:50:24 +0000 [thread overview]
Message-ID: <bug-104157-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104157
Bug ID: 104157
Summary: libc++ does not work properly with x86_64-w64-mingw32
host, but works fine with x86_64-linux-gnu host
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: unlvsur at live dot com
Target Milestone: ---
d:\x86_64-windows-gnu\aarch64-linux-android\aarch64-linux-android\include\c++\v1\cstddef:44:25:
error: no include path in which to search for stddef.h
44 | #include_next <stddef.h>
| ^
d:\x86_64-windows-gnu\aarch64-linux-android\aarch64-linux-android\include\c++\v1\cstddef:49:9:
error: 'ptrdiff_t' has not been declared in '::'
49 | using ::ptrdiff_t _LIBCPP_USING_IF_EXISTS;
| ^~~~~~~~~
d:\x86_64-windows-gnu\aarch64-linux-android\aarch64-linux-android\include\c++\v1\cstddef:50:9:
error: 'size_t' has not been declared in '::'
50 | using ::size_t _LIBCPP_USING_IF_EXISTS;
| ^~~~~~
d:\x86_64-windows-gnu\aarch64-linux-android\aarch64-linux-android\include\c++\v1\cstddef:53:9:
error: 'max_align_t' has not been declared in '::'
It cannot find the include path correctly for libc++ when host is windows.
D:\hg\fast_io\examples\0001.helloworld>aarch64-linux-android-g++ -v
Using built-in specs.
COLLECT_GCC=aarch64-linux-android-g++
COLLECT_LTO_WRAPPER=d:/x86_64-windows-gnu/aarch64-linux-android/bin/../libexec/gcc/aarch64-linux-android/12.0.1/lto-wrapper.exe
Target: aarch64-linux-android
Configured with: ../../../../gcc/configure --disable-nls --disable-werror
--target=aarch64-linux-android
--prefix=/home/cqwrteur/toolchains/gnu/x86_64-w64-mingw32/aarch64-linux-android
--enable-languages=c,c++ --disable-libstdcxx-verbose --disable-multilib
--with-gxx-libcxx-include-dir=/home/cqwrteur/toolchains/gnu/x86_64-w64-mingw32/aarch64-linux-android/aarch64-linux-android/include/c++/v1
--host=x86_64-w64-mingw32
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 12.0.1 20220121 (experimental) (GCC)
next reply other threads:[~2022-01-21 5:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 5:50 unlvsur at live dot com [this message]
2022-01-21 5:51 ` [Bug c++/104157] " unlvsur at live dot com
2022-01-21 8:43 ` pinskia at gcc dot gnu.org
2022-01-21 8:47 ` unlvsur at live dot com
2022-01-21 8:51 ` pinskia at gcc dot gnu.org
2022-01-21 8:54 ` unlvsur at live dot com
2022-01-21 9:00 ` pinskia at gcc dot gnu.org
2022-01-21 9:02 ` pinskia at gcc dot gnu.org
2022-01-21 9:07 ` unlvsur at live dot com
2022-01-21 9:08 ` unlvsur at live dot com
2022-01-21 9:18 ` [Bug c++/104157] -std=libc++ does not with cross compilers and moving the install around (places the include path last) pinskia at gcc dot gnu.org
2022-01-21 9:20 ` pinskia at gcc dot gnu.org
2022-01-21 9:36 ` unlvsur at live dot com
2022-01-21 9:38 ` pinskia 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-104157-4@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).