x86_64-pc-linux-gnu-g++ -fPIC -O2 -pipe -march=native -I. -ISource -ISource/Metadata -ISource/FreeImageToolkit -DUSE_JPEG -DUSE_MNG -DUSE_PNG -I/usr/include/libpng16 -DUSE_TIFF -I/usr/include/OpenEXR -fPIC -c Source/FreeImage/PluginJPEG.cpp -o Source/FreeImage/PluginJPEG.o Source/FreeImage/PluginJPEG.cpp: In function ‘BOOL jpeg_read_icc_profile(j_decompress_ptr, JOCTET**, unsigned int*)’: Source/FreeImage/PluginJPEG.cpp:510:1: error: ‘BOOL jpeg_read_icc_profile(j_decompress_ptr, JOCTET**, unsigned int*)’ was declared ‘extern’ and later ‘static’ [-fpermissive] jpeg_read_icc_profile(j_decompress_ptr cinfo, JOCTET **icc_data_ptr, unsigned *icc_data_len) { ^~~~~~~~~~~~~~~~~~~~~ In file included from Source/FreeImage/PluginJPEG.cpp:41:0: ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-desktop-gnome-systemd_test_20180809-181720 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.0 * Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.8.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpv media-libs/freeimage [ebuild N ] media-libs/freeimage-3.15.4-r1 USE="jpeg mng png tiff -jpeg2k -openexr -raw -static-libs"
Created attachment 543416 [details] emerge-info.txt
Created attachment 543418 [details] emerge-history.txt
Created attachment 543420 [details] environment
Created attachment 543422 [details] etc.portage.tbz2
Created attachment 543424 [details] media-libs:freeimage-3.15.4-r1:20180814-090549.log
Created attachment 543426 [details] temp.tbz2
Created attachment 545970 [details, diff] freeimage-3.15.4-rename-static.patch Patch (by me) to simply rename the static function to avoid the error.
I have the same issue. Is there any chance that the patch comes into the normal portage tree?
This works for me too. Also, there are newer versions of this library available now.
Still hitting this one...
freeimage-3.18.0-r1, which is in the tree for more than 6 months, builds fine. It should be stabilized ASAP as current stable version is broken.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=bd034ff8887960d9351529ab7fbae2b4754e4eea commit bd034ff8887960d9351529ab7fbae2b4754e4eea Author: James Le Cuirot <chewi@gentoo.org> AuthorDate: 2019-11-26 20:26:23 +0000 Commit: James Le Cuirot <chewi@gentoo.org> CommitDate: 2019-11-26 20:26:23 +0000 media-libs/freeimage: Drop old 3.15.4-r1 Closes: https://bugs.gentoo.org/663614 Package-Manager: Portage-2.3.79, Repoman-2.3.17 Signed-off-by: James Le Cuirot <chewi@gentoo.org> media-libs/freeimage/Manifest | 2 - .../files/freeimage-3.15.4-CVE-2015-0852.patch | 214 ------- .../files/freeimage-3.15.4-CVE-2016-5684-1.patch | 23 - .../files/freeimage-3.15.4-CVE-2016-5684-2.patch | 11 - .../files/freeimage-3.15.4-libjpeg-turbo.patch | 531 ----------------- .../files/freeimage-3.15.4-libjpeg9.patch | 45 -- .../freeimage/files/freeimage-3.15.4-raw.patch | 16 - .../files/freeimage-3.15.4-unbundling.patch | 639 --------------------- media-libs/freeimage/freeimage-3.15.4-r1.ebuild | 116 ---- 9 files changed, 1597 deletions(-)
