This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/65118] New: Android target build is broken with "guard.cc:36:22: fatal error: syscall.h: No such file or directory"
- From: "aivchenk at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 19 Feb 2015 13:05:54 +0000
- Subject: [Bug libstdc++/65118] New: Android target build is broken with "guard.cc:36:22: fatal error: syscall.h: No such file or directory"
- Auto-submitted: auto-generated
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65118
Bug ID: 65118
Summary: Android target build is broken with "guard.cc:36:22:
fatal error: syscall.h: No such file or directory"
Product: gcc
Version: 5.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: aivchenk at gmail dot com
configured with: /users/aivchenk/toolchain_3/gcc/gcc-5.0/libstdc++-v3/configure
- --enable-multilib --with-cross-host=x86_64-linux-gnu --disable-bootstrap
--with-sysroot=/users/aivchenk/ndk/android-ndk-r10d/platforms/android-21/arch-x86_64/
--disable-shared --disable-libitm --disable-libsanitazer
--enable-languages=c,c++,lto
--program-transform-name=s&^&x86_64-linux-android-& --disable-option-checking
--with-target-subdir=x86_64-linux-android --build=x86_64-linux-gnu
--host=x86_64-linux-android --target=x86_64-linux-android
/users/aivchenk/toolchain_3//gcc/gcc-4.10/libstdc++-v3/libsupc++/guard.cc:36:22:
fatal error: syscall.h: No such file or directory
Should we guard that with __ANDROID__?