-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build in 2 stages #6
Conversation
it isn't recognized by gcc
Started test build 54643 |
Build 54643 failed |
Started test build 54667 |
Build 54667 failed |
Started test build 54677 |
Build 54677 successful
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like this cleans all files from stage2 that exist also in stage1 and in the result not much is left there. I think we need to differentiate install path for stage1.
"config-opts": [ | ||
"-DFFI_INCLUDE_DIR=/usr/lib/x86_64-linux-gnu/libffi-3.2.1/include", | ||
"-DLLVM_DEFAULT_TARGET_TRIPLE=x86_64-unknown-linux-gnu", | ||
"-DLLVM_TARGETS_TO_BUILD='X86;AMDGPU;NVPTX'" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can leave only X86 here and drop the rest.
"-DLLVM_ENABLE_PROJECTS='clang;compiler-rt;lld'", | ||
"-DLLVM_ENABLE_ASSERTIONS:BOOL=OFF", | ||
"-DBUILD_SHARED_LIBS:BOOL=OFF", | ||
"-DLLVM_BUILD_LLVM_DYLIB:BOOL=ON", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can disable all DYLIB options in stage1 as we don't care about size there
I get it almost working here except it refuses to build sanitizers in final stage while in stage1 it builds them just fine. Something screws up feature autodetection and I ran out of ideas about how to fix it. |
I figured it out. This was caused by |
Extension size is now ~330M for x86 and ~300 for aarch64. |
Not sure this is correct, but I hope it is.