checking whether --build=x86_64-pc-linux-gnu is declared... (cached) ./configure: line 2787: 5: Bad file descriptor hB-host=x86_64-pc-linux-gnu ./configure: line 2791: syntax error near unexpected token `}' ./configure: line 2791: `} # ac_fn_c_check_decl' * ERROR: media-gfx/gimp-2.10.20-r2::gentoo failed (configure phase): * econf failed ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop-libressl-20201012-031827 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.1 [2] x86_64-pc-linux-gnu-10.2.0 * clang version 11.0.0 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/11/bin /usr/lib/llvm/11 11.0.0 Available Python interpreters, in order of preference: [1] python3.7 [2] python3.9 (fallback) [3] python3.8 (fallback) [4] python2.7 (fallback) Available Ruby profiles: [1] ruby25 (with Rubygems) [2] ruby26 (with Rubygems) [3] ruby27 (with Rubygems) * Available Rust versions: [1] rust-bin-1.47.0 [2] rust-1.47.0 * The following VMs are available for generation-2: *) AdoptOpenJDK 8.265_p01 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 system-vm The Glorious Glasgow Haskell Compilation System, version 8.8.4 timestamp(s) of HEAD at this tinderbox image: /var/db/repos/gentoo Wed Oct 21 07:05:28 AM UTC 2020 /var/db/repos/libressl Sun Oct 18 04:35:14 PM UTC 2020 emerge -qpvO media-gfx/gimp [ebuild N ] media-gfx/gimp-2.10.20-r2 USE="alsa mng udev -aalib (-aqua) -debug -doc -gnome -heif -jpeg2k -openexr -postscript -test -unwind -vector-icons -webp -wmf -xpm" CPU_FLAGS_X86="mmx sse"
Created attachment 667715 [details] emerge-info.txt
Created attachment 667718 [details] emerge-history.txt
Created attachment 667721 [details] environment
Created attachment 667724 [details] etc.portage.tbz2
Created attachment 667727 [details] media-gfx:gimp-2.10.20-r2:20201021-072209.log
Created attachment 667730 [details] temp.tbz2
Should be fixed by https://gitlab.gnome.org/GNOME/gimp/-/commit/cebeb90a87105cd6e35bcb357d53cc04c828ca21
(In reply to Sergei Trofimovich from comment #7) > Should be fixed by > https://gitlab.gnome.org/GNOME/gimp/-/commit/ > cebeb90a87105cd6e35bcb357d53cc04c828ca21 Thank you for fix and sending to upstream. I think to prepare gimp-2.99.2.ebuild as it's target appeared in upstream. Unfortunately it doesn't have this fix. I could add this patch for gimp-2.99.2 and then for next release of gimp-2.10.x.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8b01ab8d909f89fa083dba2af54d205fc24c8ae5 commit 8b01ab8d909f89fa083dba2af54d205fc24c8ae5 Author: Sergey Torokhov <torokhov-s-a@yandex.ru> AuthorDate: 2020-11-01 01:31:25 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2020-11-08 11:53:29 +0000 media-gfx/gimp: 2.99.2 version bump, unstable development preview This package could be non-keyworded as depends on >=media-libs/gegl-0.27 that isn't yet released. But GIMP developers noticed me that it was small oversight on tarball package and it's still compatible with gegl-0.4.26. The dependency therefore is dropped to gegl-0.4.26. Add patch to fix compatibility with upcoming autoconf-2.70. Bug: https://bugs.gentoo.org/750575 Signed-off-by: Sergey Torokhov <torokhov-s-a@yandex.ru> Signed-off-by: Sam James <sam@gentoo.org> media-gfx/gimp/Manifest | 1 + .../gimp/files/gimp-2.99.2_fix_autoconf-2.70.patch | 58 +++++ media-gfx/gimp/gimp-2.99.2.ebuild | 249 +++++++++++++++++++++ 3 files changed, 308 insertions(+)
Any chance this autoconf patch can be backported to gimp-2.10 release series?
(In reply to Lars Wendler (Polynomial-C) from comment #10) > Any chance this autoconf patch can be backported to gimp-2.10 release series? I'm think about restoring dropped stable gimp-2.10.18-r2 (https://bugs.gentoo.org/753635 without closing bug) with removing pygtk dependency in it and then add new revisions for all 2.10.{18,20,22}. Maybe without restoring dropped stable. Or is it sufficient to fix current issue with closing only for last gimp-2.10.22?
(In reply to Sergey Torokhov from comment #11) > > Or is it sufficient to fix current issue with closing only for last > gimp-2.10.22? Yes it is. I suppose autoconf-2.70 will not enter stable for quite a while and might even end up being p.masked in unstable because of all its breaking changes. Still, it would be nice if we can fix latest unstable packages to build with autoconf-2.70 in case a user has that installed.
ping
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e2a4fcc0a43f1c1efce3d067a75aeb96a396dd86 commit e2a4fcc0a43f1c1efce3d067a75aeb96a396dd86 Author: band-a-prend <torokhov-s-a@yandex.ru> AuthorDate: 2021-01-11 14:56:51 +0000 Commit: Lars Wendler <polynomial-c@gentoo.org> CommitDate: 2021-01-11 15:26:30 +0000 media-gfx/gimp: 2.10.22 add fix autoconf-2.70 compatibility Ported to EAPI-7. Closes: https://bugs.gentoo.org/750575 Signed-off-by: Sergey Torokhov <torokhov-s-a@yandex.ru> Closes: https://github.com/gentoo/gentoo/pull/19031 Signed-off-by: Lars Wendler <polynomial-c@gentoo.org> media-gfx/gimp/gimp-2.10.22-r2.ebuild | 213 ++++++++++++++++++++++++++++++++++ 1 file changed, 213 insertions(+)
