Using gcc-6* to compile sys-block/thin-provisioning-tools-0.5.3 fails with: error: cannot convert 'persistent_data::btree<1u, thin_provisioning::device_tree_detail::device_details_traits>::maybe_value {aka boost::optional<thin_provisioning::device_tree_d
Created attachment 433886 [details, diff] thin-provisioning-tools-0.5.3-gcc6.patch A patch to compile thin-provisioning-tools-0.5.3 with gcc-6*. boost::optional doesn't seem to implicitly cast to bool so this patch just applies some explicitly casts.
please test/check thin-provisioning-tools-0.6.1 as that's the latest in the tree. if that still fails, upstream is github, so it should be trivial for you to fork & get your patch merged there (i got a few PRs accepted in the last few days).
(In reply to SpanKY from comment #2) > please test/check thin-provisioning-tools-0.6.1 as that's the latest in the > tree. if that still fails, upstream is github, so it should be trivial for > you to fork & get your patch merged there (i got a few PRs accepted in the > last few days). Hmmm. Looks like it was already resolved in git, seemingly for a separate issue, by forcing g++-98 dialect: https://github.com/jthornber/thin-provisioning-tools/commit/8b792f5c79b68a63afbe155fc3924b3a0a750e24
Hello there! This bug affects me also Mein output of 'emerge --info' https://paste.pound-python.org/show/A4dXW34qq4nxwGIg1Bcj Also I have installed GCC 6.2.0 and sys-block/thin-provisioning-tools-0.6.1 Nothing fixed. Please as was 6.2.0 released, prepare patch. Thank You!
(In reply to Oleksii from comment #4) > Hello there! > > This bug affects me also > Mein output of 'emerge --info' > https://paste.pound-python.org/show/A4dXW34qq4nxwGIg1Bcj > > Also I have installed GCC 6.2.0 and sys-block/thin-provisioning-tools-0.6.1 > Nothing fixed. Please as was 6.2.0 released, prepare patch. > Thank You! Or put thin-provisioning-tools-0.6.2 or thin-provisioning-tools-0.6.3 in the portage tree since this was fixed in 0.6.2-rc3.
This is duplicate of bug 598424
(In reply to moikkis from comment #6) thanks. this one is older, but that one is fixed, so easier to dupe that way. *** This bug has been marked as a duplicate of bug 598424 ***