chakra-core / chakra-core/ChakraCore

[macOS | Building] error with 'cstdint' file not found while build for macOS 10.7

Open
#3,519 5 comments 0 reactions 0 assignees View on GitHub
Out of Scope
Dominant language
JavaScript
Stars
9.3k
Forks
1.2k
PR merge metrics
No merged PRs in 30d

Description

```
[ 13%] Building CXX object pal/src/CMakeFiles/Chakra.Pal.dir/thread/threadsusp.cpp.o
[ 13%] Building CXX object pal/src/CMakeFiles/Chakra.Pal.dir/exception/machexception.cpp.o
[ 13%] Building CXX object pal/src/CMakeFiles/Chakra.Pal.dir/exception/machmessage.cpp.o
[ 13%] Building ASM object pal/src/CMakeFiles/Chakra.Pal.dir/arch/i386/activationhandlerwrapper.S.o
[ 13%] Building ASM object pal/src/CMakeFiles/Chakra.Pal.dir/arch/i386/dispatchexceptionwrapper.S.o
[ 13%] Building ASM object pal/src/CMakeFiles/Chakra.Pal.dir/arch/i386/context2.S.o
[ 13%] Building ASM object pal/src/CMakeFiles/Chakra.Pal.dir/arch/i386/debugbreak.S.o
[ 14%] Building CXX object pal/src/CMakeFiles/Chakra.Pal.dir/arch/i386/processor.cpp.o
[ 14%] Building ASM object pal/src/CMakeFiles/Chakra.Pal.dir/arch/i386/asmhelpers.S.o
[ 14%] Built target Chakra.Pal
Scanning dependencies of target libwabt
[ 14%] Building CXX object lib/wabt/CMakeFiles/libwabt.dir/src/prebuilt/wast-lexer-gen.cc.o
In file included from src/wast-lexer.cc:17:
In file included from /Volumes/T3/RemotesCommity/node-chakracore/deps/chakrashim/core/lib/wabt/src/wast-lexer.h:24:
/Volumes/T3/RemotesCommity/node-chakracore/deps/chakrashim/core/lib/wabt/src/common.h:23:10: fatal error: 'cstdint' file not found
#include
^
error generated.
make[2]: *** [lib/wabt/CMakeFiles/libwabt.dir/src/prebuilt/wast-lexer-gen.cc.o] Error 1
make[1]: *** [lib/wabt/CMakeFiles/libwabt.dir/all] Error 2
make: *** [all] Error 2
See error details above. Exit code was 2
```

i try setting up the build target to `latest` macOS and everything go fine

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.