-
Notifications
You must be signed in to change notification settings - Fork 82
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
compiling with _GLIBCXX_DEBUG gives errors #3221
Comments
Hey there, I'll look at this on Wednesday (still on holiday today and tomorrow). It should only use constexpr vectors if the compiler supports it and our nightlies with glibcxx_debug also work, but they might just not cover your use case. Do you have a minimal example that fails to compile? I. E., how do you use the alphabet vector? |
I can confirm this bug on godbolt with the newest seqan version (it works with seqan 3.2.0): |
I believe this is a bug in gcc/libstdc++ I found this entry on bugzilla, showing at least one person is aware of this issue: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104748 To solve this, we don't guarentee that |
I suggested following fix: #3222 |
Does this problem persist on the current master?
Is there an existing issue for this?
Current Behavior
Compiling a seqan3-dependent program with -D_GLIBCXX_DEBUG (debug mode) gives errors that don't happen without debug mode:
Expected Behavior
We'd like to compile a seqan3-dependent program under C++20 standard in debug mode, without errors.
Steps To Reproduce
Add -D_GLIBCXX_DEBUG when compiling.
Environment
Anything else?
As always, thanks for your work on seqan!
@eseiler
The text was updated successfully, but these errors were encountered: