-
Notifications
You must be signed in to change notification settings - Fork 371
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
Fix 990 / Compilation issues with C++11 and libc++ #993
Conversation
…. Makes check robust for C++11 on all systems.
@ikitayama @carlosengutierrez This PR should solve the |
@heplesser the build's been going smoothly (97% done), as you know the Fujitsu toolchain takes couples of hours to complete build, so I'll let you know when it's done around midnight here. |
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.
Looks good to me, and compiles and runs without problems using both Clang-6.0 and GCC-8 with -std=c++11
.
confirmation (including make installcheck) will be done sometime tomorrow. |
@carlosengutierrez are you finished building the 5g branch with FCC natively? Here it's been running for 2 hours, but still going. |
Hi @ikitayama , |
You could use screen so that your build job don't get terminated. |
@heplesser the cross build with FCC with the -DCMAKE_CXX_FLAGS="-Xg -std=c++11" on the frontend of K computer successfully finished. Took about 3 hours. |
@ikitayama Excellent, thank you! |
I have added another commit, which automatically includes the |
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.
Alright then, I guess this is ready to be merged.
Thanks @heplesser for solving this issue and thanks @ikitayama and @carlosengutierrez for testing!
@heplesser I could compile the updated nest master branch. PYNEST is running. |
@carlosengutierrez Excellent, thank you for testing! |
Note that the issues fixed here do not occur with gcc and libstdc++, they only occur with LLVM/Clang compilers using libc++ in C++11 mode and with some other compilers that do not use libstdc++.