-
-
Notifications
You must be signed in to change notification settings - Fork 604
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
On pagecache.cc, boost::addressof() fails to compile on gcc 5.1.1 #632
Comments
I can confirm this. The build fails with the exact same message stated above. Patching it manually seems to fix the issue. Maybe it's time for a version bump of boost in misc.bin? |
Itaru Kitayama reported the same problem back in April, and Gleb discovered it was probably solved by updating to Boost 1.56: see discussion in https://groups.google.com/forum/#!topic/osv-dev/ZegZnCBtZTY I don't know what to suggest... Updating external/ to Boost 1.56 means updating the basis of our "external" directory to Fedora 22, which just came out a few days ago, and likely to only work correctly with the gcc in that distro (gcc 5.1). I doubt this is a good idea. One solution I think we need to seriously consider not to use external/, which was a good idea ("make builds repeatable") but has proven to be unmaintainable, as more and more stuff (more importantly - the compiler itself) is taken from the host and doesn't work together with what we put in external/. Another option that doesn't make me happy at all, but is possible, is to have multiple versions in external/: We'll have boost 1.55 from Fedora 21 for hosts with gcc 4.9, and boost 1.56 from Fedora 22 for hosts with gcc 5.1. |
I just posted to the OSv mailing list a patch for issue #633. After this patch, the OSv build should by default (boost_env=host is the default) take the Boost headers installed on the build machine, not from the "external/" directory. On systems which have gcc 5.1, the installed boost will surely be >= 1.56, so this bug should no longer occur. Can someone who can reproduce this bug please check if my patch for issue #633 also fixes this bug (when boost_env=external is not used)? |
Takuya, should we close this issue? |
Ping on the question if we can close this issue? |
It seems boost library bug.
ticket: https://svn.boost.org/trac/boost/ticket/5487
commit: boostorg/core@779e2b3
patch: https://github.com/boostorg/core/commit/779e2b30def02f414906a02f0b6c12ff97ca5efb.patch
I confirmed that it able to compile with the patch.
The commit seems included on boost 1.56 or later, so we probably should update boost version.
Or we also can apply the patch on misc.bin repository (that's what I tested).
Console output attached.
The text was updated successfully, but these errors were encountered: