-
Notifications
You must be signed in to change notification settings - Fork 7
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
Failed to build #7
Comments
I'm not familiar with GCC 10. From what I can tell, GCC 10 has not been official released; it's still a work-in-progress. You might try installing the current stable release of GCC. I would also recommend trying to build a newer version of Tapir than what the Tapir-Meta currently points to. Newer versions of the Tapir and LLVM codebases include changes that are necessary to accommodate updates to the C++ standard, various compiler defaults, and standard libraries. |
I tried switching to gcc 9.2, the most recent stable version and am able to get through the configuration to the build step and it fails with a I am on a machine without cilk, so I wonder if it is a requirement to have cilk on the machine before installing tapir. |
You should not need Cilk on the machine to build and install Tapir. Can you provide more context for that error message? (In other words, what were the commands you ran, and what command failed with that error message?) |
I ran
I failed with
I have since managed to get farther into the build process by switching to gcc 4.9, which did include cilk, but I had to make a few changes. I think they were related to the fact that older versions of gcc did not handle static asserts the same. I first tried using CMAKE_C_FLAGS and CMAKE_CXX_FLAGS to enable c11 and c++11 features but ended up having to make the following changes to get it past a few errors compiling.
The errors I was avoiding were
and
The build step with the changes above is still in process and I will update if that fixes things. I post now since regardless of if it works there still seems to be a bug in compiling on either old systems and systems without cilk. |
Regarding the first problem, it appears that GCC is deprecating Cilk in a manner that messes up CMake's ability to tell whether or not the compiler supports Cilk. For now, you can work around this issue by passing the flag |
When I first try and build using
./build.sh release
I get
CMake Error at cmake/modules/CheckCompilerVersion.cmake:12 (message): Host GCC version must be at least 4.8! Call Stack (most recent call first): cmake/config-ix.cmake:14 (include) CMakeLists.txt:594 (include)
This is because on the host machine the default g++ and gcc are 4.4.7
However, I have installed gcc 10.0.0 in my path, but it doesn't seem to find them and I did not find the proper way to specify them.
I tried to specify them by changing the following line in the build.sh script
line 54:
cmake $MODE -DLLVM_TARGETS_TO_BUILD=host $LLVM_SRC
to:
cmake $MODE -DLLVM_TARGETS_TO_BUILD=host -DCMAKE_C_COMPILER=/home/wheatman/install_dir/gcc/bin/gcc -DCMAKE_CXX_COMPILER=/home/wheatman/install_dir/gcc/bin/g++ $LLVM_SRC
Which I thought would set it up to use the correct compiler and it seems to get through the configuration, then fails when building.
The output is attached.
pane.txt
Let me know what other details you need or how I can fix this problem.
The text was updated successfully, but these errors were encountered: