-
Notifications
You must be signed in to change notification settings - Fork 81
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
Compilation fails on RPi2B + Arch + distcc #92
Comments
What clang version do you have? What does Judging by the error it looks like the command for you would be:
|
|
And just running |
Sorry, I didn't read that correctly: However, it was installed here:
|
Can distcc even compile to SPIR? |
To give a little bit more context: VC4C(L) should be able to be compiled with any C++14 able compiler, including distcc. But, additionally to that the VC4C compiler requires a clang (at runtime) to compile the OpenCL C sources to either a LLVM IR module or SPIR-V binary code (depending on the build configuration of VC4C). It looks like in your build, you also configured to use distcc here (see output |
I successfully installed using pacman: VC4C and VC4CLstlib. With VC4CL I have a pre-compilation error? I appreciate the above follow-up and the explanation. While right now the RPi is setup to invoke The errors above:
and
happen at VC4CL "compilation time" and not at "runtime"? |
Yes, because at the end of the VC4C compilation, the The error looks like distcc does not know the Can you run the following command and paste the output?
This is the command that will be invoked at the end of compilation. Maybe a more verbose log output gives is some useful information... |
I got:
I can try to disable |
Alternatively, it is possible to bypass any front-end of |
Can you run
I don't understand what you mean. The clang front-end is hard-coded into the VC4C executable on compilation. It is used as I said before for OpenCL C -> LLVM IR compilation. If you at runtime never pass OpenCL C code to the VC4CL implementation, the front-end is never used.
|
Sorry, I was unclear. For me distcc is a front-end of clang. Can't you bypass any front-end of clang and invoke clang directly from vc4c (i.e. hard code a path? Or have an optoin to identify clang's path)? And:
|
I am using a hardcoded path to clang (see the output of Given the error message, that it fails on the Can you reconfigure and rebuild VC4C with the CMake option |
I assume my
cmake/clang.cmake, lines 14-25:
clang --version
I tried to print
|
Strange, manual tests using "clang version 10.0.0" as The CMake variable As a side note, in the code snippet you pasted, in the line
there should be a
|
I made a mistake when setting CLANG_FOUND variable. I initially set it to Compiling, and:
Clean build make no difference. WIll have to look at all the output but see nothing obvious. |
OK, I did find this message that surprised me:
That is maybe because it wasn't needed here (on the first line):
|
To be clear, I am compiling this package: https://aur.archlinux.org/packages/vc4c-git/ Looking at the error
So the following line in the cmake file seems to have an empty variable for
|
To be able to build VC4C, you also need the sources for VC4CLStdLib. There are several options where the VC4C CMake autodetects the location of the VC4CLStdLib sources:
In any other constellation, you need to specify the Note: This is only required for building, on "normal" runtime, the VC4C compiler also checks the |
The first error I got could be fixed with this code:
doe300/VC4C#145 (comment)
But the second error:
The text was updated successfully, but these errors were encountered: