-
Notifications
You must be signed in to change notification settings - Fork 701
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 step fails for manta-1.6.0-GCC-10.2.0-Python-2.7.18.eb #13337
Comments
Installation of So the problem seems to be that |
When using
and then the compiler command for In the failing build, without
And then there's no So an obvious fix would be to add |
Some more info: Also, this problem is not popping up at all with And yep: boostorg/type_traits#107 So I'll just work around this by adding |
I don't think this is an appropriate fix because it only does a workaround which happens to work. The actual problems in order are:
--> Better fix is to not enable Werror from manta by changing this here to false: https://github.com/Illumina/manta/blob/75b5c38d4fcd2f6961197b28a41eb61856f2d976/CMakeLists.txt#L56 as is done in their actual releases: https://github.com/Illumina/manta/blob/75b5c38d4fcd2f6961197b28a41eb61856f2d976/scratch/make_release_tarball.bash#L63 |
Or just use the actual release sources: https://github.com/Illumina/manta/releases/download/v1.6.0/manta-1.6.0.release_src.tar.bz2 |
As per the design of the IMPORTED targets (i.e. for Boost_NO_BOOST_CMAKE=OFF) the include paths are always SYSTEM while they are NOT for the FindBoost versions. However due to some legacy targets they are BOTH added as SYSTEM. Or should be. |
Ok, it is a bug in manta: Illumina/manta#265 Anyway: Using the release builds will (likely) have worked but given their use of CMake the current solution is acceptable |
manta-1.6.0-GCC-10.2.0-Python-2.7.18.eb
installs fine with EasyBuild, even on top of a Boost that was installed with the enhanced easyblock from easybuilders/easybuild-easyblocks#2456.It looks like this issue could be related to the changes in easybuilders/easybuild-easyblocks#2461...
The text was updated successfully, but these errors were encountered: