./AADevice.cpp:41:19: note: candidate: template<int PIXELCOL> fim_err_t AADevice::clear_rect_(void*, fim_coo_t, fim_coo_t, fim_coo_t, fim_coo_t, fim_coo_t)’ 41 | fim_err_t AADevice::clear_rect_( | ^~~~~~~~ ./AADevice.cpp:41:19: note: template argument deduction/substitution failed: ./AADevice.cpp:492:58: error: narrowing conversion of 4294967295’ from unsigned int’ to int’ [-Wnarrowing] 492 | return clear_rect_<FIM_CNS_WHITE>(aa_image(ascii_context_),y1, x1, y2-y1+1, x2-x1+1,aa_imgwidth(ascii_context_)); | ~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop_plasma-j4-20220629-110005 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-12.1.1 * clang/llvm (if any): clang version 14.0.6 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/14/bin /usr/lib/llvm/14 14.0.6 Python 3.9.13 Available Ruby profiles: (none found) Available Rust versions: [1] rust-1.61.0 * The following VMs are available for generation-2: 1) Eclipse Temurin JDK 11.0.15_p10 [openjdk-bin-11] *) Eclipse Temurin JDK 17.0.3_p7 [openjdk-bin-17] 3) Eclipse Temurin JDK 8.332_p09 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 [2] openjdk-bin-11 [3] openjdk-bin-17 system-vm The Glorious Glasgow Haskell Compilation System, version 8.10.4 php cli: HEAD of ::gentoo commit 33a769661a645afff1c40969acf0d4457862fbd6 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Thu Jun 30 23:01:31 2022 +0000 2022-06-30 23:01:31 UTC emerge -qpvO media-gfx/fim [ebuild N ] media-gfx/fim-0.5_rc3 USE="aalib exif gif jpeg png readline sdl svg tiff -bmp -dia -djvu -fbcon -graphicsmagick -imagemagick -pcx -pdf -postscript -static -xfig"
Created attachment 789236 [details] emerge-info.txt
Created attachment 789239 [details] emerge-history.txt
Created attachment 789242 [details] environment
Created attachment 789245 [details] etc.portage.tar.bz2
Created attachment 789248 [details] logs.tar.bz2
Created attachment 789251 [details] media-gfx:fim-0.5_rc3:20220701-003457.log
Created attachment 789254 [details] temp.tar.bz2
No release in a long time but https://svn.savannah.gnu.org/viewvc/fbi-improved/trunk/src/AADevice.cpp?r1=803&r2=844 might help. The website actually advertises using trunk.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=feedef9b8a74d9e20cfb65ee1ccd2c336c3fd1cc commit feedef9b8a74d9e20cfb65ee1ccd2c336c3fd1cc Author: Michał Górny <mgorny@gentoo.org> AuthorDate: 2023-02-24 18:06:22 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2023-02-24 20:04:10 +0000 package.mask: Last rite media-gfx/fim Bug: https://bugs.gentoo.org/855548 Signed-off-by: Michał Górny <mgorny@gentoo.org> profiles/package.mask | 6 ++++++ 1 file changed, 6 insertions(+)
I emailed upstream about this error a few weeks ago. Note that this build failure only happens when `USE=aalb`. This was included in the response I got: > fim-0.5_rc3 is mega-old ! > Can you please check out the latest tarball > http://download.savannah.nongnu.org/releases/fbi-improved/fim-0.6-trunk.tar.gz > ? > I wish to release it ASAP (I mean, really :-) ) I got an unrelated build failure both when building it by hand and putting this in the SRC_URI of our current ebuild. I haven't had much time to debug it lately. Once 0.6 drops (and I work out this current other build failure) could we revert fim's removal? I would be happy to step in to proxy maintain.
(In reply to Red from comment #10) > I emailed upstream about this error a few weeks ago. Note that this build > failure only happens when `USE=aalb`. This was included in the response I > got: > > > > fim-0.5_rc3 is mega-old ! > > Can you please check out the latest tarball > > http://download.savannah.nongnu.org/releases/fbi-improved/fim-0.6-trunk.tar.gz > > ? > > I wish to release it ASAP (I mean, really :-) ) > > I got an unrelated build failure both when building it by hand and putting > this in the SRC_URI of our current ebuild. I haven't had much time to debug > it lately. > > Once 0.6 drops (and I work out this current other build failure) could we > revert fim's removal? I would be happy to step in to proxy maintain. sounds good!
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=239e38343df04f26115a3b414b3da80b2b220ec2 commit 239e38343df04f26115a3b414b3da80b2b220ec2 Author: David Seifert <soap@gentoo.org> AuthorDate: 2023-03-26 10:56:50 +0000 Commit: David Seifert <soap@gentoo.org> CommitDate: 2023-03-26 10:56:50 +0000 media-gfx/fim: treeclean Closes: https://bugs.gentoo.org/796407 Closes: https://bugs.gentoo.org/855548 Closes: https://bugs.gentoo.org/889254 Closes: https://bugs.gentoo.org/889928 Closes: https://bugs.gentoo.org/896208 Signed-off-by: David Seifert <soap@gentoo.org> media-gfx/fim/Manifest | 1 - media-gfx/fim/files/fim-0.4_rc3-poppler031.patch | 12 --- media-gfx/fim/files/fim-0.5_rc3-deg-symbol.patch | 14 --- media-gfx/fim/files/fim-0.5_rc3-jpeg-9c.patch | 26 ------ media-gfx/fim/files/fim-0.5_rc3-jpeg.patch | 13 --- media-gfx/fim/files/fim-0.5_rc3-libsdl.patch | 27 ------ media-gfx/fim/fim-0.5_rc3-r1.ebuild | 103 ----------------------- media-gfx/fim/metadata.xml | 15 ---- profiles/package.mask | 6 -- 9 files changed, 217 deletions(-)
