auto callbacks = lock(_callback_list); ^ utils.hxx:675:18: error: range-based ‘for’ expression of type ‘auto’ has incomplete type for(auto func: callbacks) { ^~~~~~~~~ In file included from dropdown_menu.cxx:10:0: ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-desktop_20171121-221602 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.2.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python3.6 (fallback) [3] python2.7 (fallback) Available Ruby profiles: [1] ruby22 (with Rubygems) * java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.6.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpv x11-wm/page [ebuild N ] x11-wm/page-1.9.9
Created attachment 506618 [details] emerge-info.txt
Created attachment 506620 [details] emerge-history.txt
Created attachment 506622 [details] environment
Created attachment 506624 [details] etc.portage.tbz2
Created attachment 506626 [details] logs.tbz2
Created attachment 506628 [details] temp.tbz2
Created attachment 506630 [details] x11-wm:page-1.9.9:20171125-162355.log
Created attachment 507696 [details, diff] Fix functionnal include for gcc-7+ Hello, Thank you for reporting this bug. Can you try the attached patch and tell me if that work for you? You just have to copy the patch to the following directory : /etc/portage/patches/x11-wm/page and them emerge page again. At begin of the merge of page you should see Applying patch with the name of the file you put in the patch directory. Thanks by advance, best regards.
Hey Benoit Thanks for picking this up. If the patch is necessary to get page to compile with GCC 7 and above, I can add it to the tree ASAP. Let me know. Thanks!
Better yet, fix the bug and cut a release. We'll create a new ebuild for it. What do you think?
patch is ok and fixes the issue
Created attachment 507744 [details] New ebuild including the patch Hello Clement, I attached a new ebuild including the patch that fix the issue. @Toralf: Thanks for your feedback. Best regards
(In reply to Benoit Gschwind from comment #12) > Created attachment 507744 [details] > New ebuild including the patch > > Hello Clement, > Patrice = mon prénom Clement = mon nom de famille :)
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2aeb7837a366e41884c2b3dddaf56355801a0082 commit 2aeb7837a366e41884c2b3dddaf56355801a0082 Author: Patrice Clement <monsieurp@gentoo.org> AuthorDate: 2017-12-04 20:34:49 +0000 Commit: Patrice Clement <monsieurp@gentoo.org> CommitDate: 2017-12-04 20:35:00 +0000 x11-wm/page: version bump. Closes: https://bugs.gentoo.org/585452 Closes: https://bugs.gentoo.org/638844 Package-Manager: Portage-2.3.13, Repoman-2.3.3 x11-wm/page/Manifest | 3 ++- x11-wm/page/page-1.9.9-r1.ebuild | 50 ++++++++++++++++++++++++++++++++++++++++ 2 files changed, 52 insertions(+), 1 deletion(-)
