-
Notifications
You must be signed in to change notification settings - Fork 9
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
KMC compilation error when compiling from source #45
Comments
Can you say what version of GCC or clang you are using? Sometimes compilers update and break in an incompatible way (the newer compilers are stricter). We generally test on GCC 11, so there may be compilation problems on GCC 13 we aren't catching. |
|
hi @rob-p , any idea if this issue will be addressed? |
Can you please see if it's addressed on the develop branch, @Sawwave? If so, we can merge into master, but we don't have a copy of a new enough GCC on our development machine to test locally. |
Unfortunately, it seems to still have build errors. I've included the first few pages of the errors when make is run
We can use the conda package, so this isn't a blocker on our end, but it's likely something you will want to address at some point. Thank you for looking into this. |
Thanks for the update. The KMC reliance on undeclared types under the newer compiler seems to be killing us. I’ll try and set up a newer GCC somewhere to test this and see what can be easily patched. |
Hi @Sawwave, Can you try on develop once more? I made a docker image with ubuntu 24.04 and gcc-14 and fixed the patch so that KMC (and cuttlefish) now seem to properly compile. Thanks! |
Still get a few errors, but it's a lot less this time! Here's all the error I received.
|
When compiling cuttlefish from source, the included kmc_core seems to have compilation errors due to an incorrect #include.
Specifically, the following errors are generated.
Is the wrong KMC version being downloaded with curl in the cmake build? Currently, the cmake file specifies the following for KMC:
The text was updated successfully, but these errors were encountered: