-
Notifications
You must be signed in to change notification settings - Fork 108
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
abyss-2.1.0: cannot enable sparsehash due to gcc-5.4.0 with gomp #225
Comments
Hmm, I'm not sure what the issue is. It does indeed look like sparsehash fails to compile with that particular gcc. I am wondering if sparsehash has changed its minimum requirements, or if you are somehow using a development/experimental version of sparsehash. Could you post any info you can find about the version of sparsehash on your system? Below I have posted what I believe the relevant area of
|
It is dev-cpp/sparsehash-2.0.3-r1::gentoo. I thought it could maybe be some issue with headers copied&fixed aside by gcc (it used to poke through headers in /usr/include and correct them in its own copies. Just in case:
|
Hmm. sparsehash-2.0.3 is the most recent release, which was published way back in Oct 2015. It is quite possible that there are some gentoo-specific patches to sparsehash that are breaking ABySS compilation. My guess is that there is a gentoo patch to sparsehash that requires compiling in "C++11" mode (ABySS normally compiles in "C++98" mode). You could test that theory by adding the word |
If your goal is just to install ABySS, you may wish to try installing ABySS using Linuxbrew. See http://linuxbrew.sh/ then If your goal is to fix the Gentoo portage package of ABySS, the Homebrew formula may be a useful reference: |
Thanks, Shaun. |
@benvvalk Yes, there is a patch at https://packages.gentoo.org/packages/dev-cpp/sparsehash distributed along 2.0.3-r1. True, the
Thank you @sjackman , unfortunately the linuxbrew formula does not really help me. I am scratching my head what As I see also with gcc-5.4.0 I am not getting ABYSS-P out, so this blind shot at using older gcc versions was not really helpful anyway. |
Compiling |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
keeping this one open until fixed |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Hi,
I am trying older gcc versions and I received:
Looking into
config.log
I see:build.log.txt
config.log.txt
The text was updated successfully, but these errors were encountered: