https://tracker.ceph.com/https://tracker.ceph.com/favicon.ico2018-01-05T19:56:10ZCeph rgw - Bug #22600: compilation failures with boost 1.66https://tracker.ceph.com/issues/22600?journal_id=1044192018-01-05T19:56:10ZCasey Bodleycbodley@redhat.com
<ul></ul><p><a class="external" href="https://github.com/ceph/ceph/pull/19808">https://github.com/ceph/ceph/pull/19808</a></p> rgw - Bug #22600: compilation failures with boost 1.66https://tracker.ceph.com/issues/22600?journal_id=1044222018-01-05T20:57:25ZCasey Bodleycbodley@redhat.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Fix Under Review</i></li></ul> rgw - Bug #22600: compilation failures with boost 1.66https://tracker.ceph.com/issues/22600?journal_id=1044432018-01-05T21:56:55ZCasey Bodleycbodley@redhat.com
<ul></ul><p>i'm conflicted about what to backport for luminous. there have been quite a few beast frontend changes in radosgw that haven't been backported (<a class="external" href="https://github.com/ceph/ceph/pull/17923">https://github.com/ceph/ceph/pull/17923</a> <a class="external" href="https://github.com/ceph/ceph/pull/17977">https://github.com/ceph/ceph/pull/17977</a> <a class="external" href="https://github.com/ceph/ceph/pull/18402">https://github.com/ceph/ceph/pull/18402</a> <a class="external" href="https://github.com/ceph/ceph/pull/19182">https://github.com/ceph/ceph/pull/19182</a> being the major ones), so luminous still targets an old branch of the beast submodule. that old beast code uses stuff in boost::asio that doesn't build against boost 1.66. so i think we either need to backport everything related to the beast frontend, or disable the build of it entirely - and i'm not particularly happy with either of those options</p> rgw - Bug #22600: compilation failures with boost 1.66https://tracker.ceph.com/issues/22600?journal_id=1045302018-01-08T21:55:50ZCasey Bodleycbodley@redhat.com
<ul><li><strong>Status</strong> changed from <i>Fix Under Review</i> to <i>Pending Backport</i></li></ul> rgw - Bug #22600: compilation failures with boost 1.66https://tracker.ceph.com/issues/22600?journal_id=1045312018-01-08T21:57:46ZCasey Bodleycbodley@redhat.com
<ul><li><strong>Copied to</strong> <i><a class="issue tracker-9 status-3 priority-4 priority-default closed" href="/issues/22621">Backport #22621</a>: luminous: compilation failures with boost 1.66</i> added</li></ul> rgw - Bug #22600: compilation failures with boost 1.66https://tracker.ceph.com/issues/22600?journal_id=1048672018-01-16T09:40:32ZNathan Cutlerncutler@suse.cz
<ul></ul><p>@Casey Is luminous really on boost 1.66? (I currently have no idea how to find out which boost version we're using, so I ask lamely. . . .)</p> rgw - Bug #22600: compilation failures with boost 1.66https://tracker.ceph.com/issues/22600?journal_id=1049292018-01-16T14:58:17ZCasey Bodleycbodley@redhat.com
<ul></ul><p>Hi Nathan,</p>
<p>boost 1.66 added some breaking changes, so this pr fixed those and updated our cmake to require 1.66 (from 1.63). the luminous codebase won't currently build with boost 1.66, so we need to backport the same fixes there. and as a result, luminous will also require 1.66</p>
<p>(p.s. our cmake build will download/build the target boost version if the system package doesn't meet our version requirement)</p> rgw - Bug #22600: compilation failures with boost 1.66https://tracker.ceph.com/issues/22600?journal_id=1064762018-02-01T23:06:55ZNathan Cutlerncutler@suse.cz
<ul><li><strong>Status</strong> changed from <i>Pending Backport</i> to <i>Resolved</i></li></ul>