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
Unable to build on Fedora 34 #86
Comments
After some searching around, I did the following, ran
Then, ran the command for building the C++ DP library and got the following errors:
|
Seems like this is a known issue in BoringSSL with gcc 11. Can you include the results of I assume you're probably using version 11. We run continuous integration with gcc 9. I can look into upgrading our BoringSSL version (looks like this should be fixed at head), or you can also downgrade your compiler to match what we're testing with. |
The BoringSSL update should be released next week. |
The results of
|
I think you're missing the first line of output with the version number? What I get is
|
I updated my comment. I improperly formatted the text. So, indeed I am using gcc version 11 instead of gcc 9 which is what is currently being used with BoringSSL. |
We updated our BoringSSL version on Monday. Try pulling and building again - I think it should work with gcc 11 now. |
I'm getting closer now but I'm still unable to build the entire thing. The new error messages I get are the following:
|
Hmm. That's not a very descriptive error message. There should be some cmake logs - mine were in I'll also note that kissfft is only required for the accounting library, so getting it to build may not be necessary, depending on what you're trying to do. But it would be good to get it working, if you're up to help. |
I've tried running the build again and now get a different error that's more akin to the original error I was getting:
|
After setting some PATHs related to gcc and g++:
I now get the following errors:
|
Could you try running with I suspect you're running into a similar error as this stackoverflow question. It seems like your export statements aren't doing what they're supposed to do, and bazel is still calling ccache instead of gcc/g++. You could try to troubleshoot why ccache is still being called, or you could use the Which version of bazel are you using? |
Output from adding
Then I ran the command with the
|
Ah, sorry, the Looks like the export statements are failing because the compilation is being run with |
I tried running it with
|
Try running it with And if you get more of the |
I think that the initial compilation problems have been solved for the most part.
|
Got it, we're back to that error. Can you see if you can find the cmake logs for kissfft? Mine are in |
Here are the logs:
|
The problem is that bazel is looking for
to the kissfft build rule in
A permanent fix would require us to be able to configure the directory when building kissfft, but they don't offer that option. Sending them a PR is probably not something I will have time to do in the short-medium term. |
Using all of these steps, I've finally been able to successfully compile this library. Thank you for your patience @dasmdasm ! |
I'm in the process of building the cpp library for DP building blocks and get the following errors:
I previously installed bazelisk and am able to run bazel.
The text was updated successfully, but these errors were encountered: