-
Notifications
You must be signed in to change notification settings - Fork 767
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
Known Issues Section #681
Known Issues Section #681
Conversation
I tried on Ubuntu 16.04 with Boost 1.68, compiled locally with gcc 5.4 (not from PPA), and the problem persists. It appears that the compiler matters, too. I think it's better to document this issue in the readme or install notes under "Known Issues" than to force users to upgrade Boost because Ubuntu 16.04 with Boost 1.58 is still widely used. A CMake warning might be ok, too. |
This reverts commit e8d7173.
@chrisbeall interesting. What would be the minimum supported compiler for GCC? We use GCC 5.5.0 in the CI and but turn off march_native. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not ideal, but this is probably a good deal: reporting the known issues which we have not been able to fix or would require users to upgrade to fix a bug in a part (serialization) that they may not need at all for their projects.
I defer the PR approval to Frank or other core developers, since this is more a "policy" than a technical discussion.
@jlblancoc I updated the PR to only have the known issues section. Does it look good to you? |
Added a new section in
INSTALL.md
for known issues which discusses conditions for the issue in #590.