echo -e "#include <gdk-pixbuf/gdk-pixdata.h>\n#if __GNUC__ >= 4\n#pragma GCC diagnostic push\n#pragma GCC diagnostic ignored \"-Wpointer-sign\"\n#endif\n" > resources/coat_of_arms_nl.c gdk-pixbuf-csource --struct --extern --name `basename resources/coat_of_arms_nl.jpg .jpg` resources/coat_of_arms_nl.jpg >> resources/coat_of_arms_nl.c failed to load "resources/coat_of_arms_nl.jpg": Couldn't recognize the image file format for file 'resources/coat_of_arms_nl.jpg' make[2]: *** [Makefile:1399: resources/coat_of_arms_nl.c] Error 1 make[2]: Leaving directory '/var/tmp/portage/app-crypt/eid-mw-4.2.0/work/eid-mw-4.2.0/plugins_tools/eid-viewer' make[1]: *** [Makefile:476: all-recursive] Error 1 ----------------------------------------------------------------- This is an unstable amd64 chroot image (named hardened-no-multilib-libressl-unstable_20170204-152815) at a hardened host acting as a tinderbox. ----------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-6.3.0 * llvm-config --version: 3.9.1 Available Python interpreters, in order of preference: [1] python3.4 [2] python2.7 (fallback) java-config: -----------------------------------------------------------------
Created attachment 462614 [details] emerge-info.txt
Created attachment 462616 [details] app-crypt:eid-mw-4.2.0:20170206-135444.log
Created attachment 462618 [details] config.log
Created attachment 462620 [details] emerge-history.txt
Created attachment 462622 [details] environment
Created attachment 462624 [details] etc.portage.tbz2
Waiting a new release, just do : # USE="jpeg" emerge -1 gdk-pixbuf And then, emerge eid-mw
(In reply to Vincent Hardy from comment #7) > Waiting a new release, just do : > > # USE="jpeg" emerge -1 gdk-pixbuf > > And then, emerge eid-mw Shouldn't we put it to dependencies then?
Created attachment 463470 [details] fixed live ebuild
Created attachment 463472 [details] fixed 4.2.0 ebuild
(In reply to Amy Liffey from comment #8) > (In reply to Vincent Hardy from comment #7) > > Waiting a new release, just do : > > > > # USE="jpeg" emerge -1 gdk-pixbuf > > > > And then, emerge eid-mw > > Shouldn't we put it to dependencies then? You are right Amy. I thought to wait for the new eid-mw release to fix this bug for good so as not to urge you too often for commit :-) I set 2 fixed ebuild in attachment (eid-4.2.0 and eid-9999). You can commit them. with kind regards, Vincent
(In reply to Vincent Hardy from comment #11) > (In reply to Amy Liffey from comment #8) > > (In reply to Vincent Hardy from comment #7) > > > Waiting a new release, just do : > > > > > > # USE="jpeg" emerge -1 gdk-pixbuf > > > > > > And then, emerge eid-mw > > > > Shouldn't we put it to dependencies then? > > You are right Amy. > > I thought to wait for the new eid-mw release to fix this bug for good so as > not to urge you too often for commit :-) > > I set 2 fixed ebuild in attachment (eid-4.2.0 and eid-9999). > You can commit them. > > with kind regards, > > Vincent commit 5f98d057f9e43ec1ba03eb0751728099cc15511b Author: Amy Liffey <amynka@gentoo.org> Date: Sun Feb 12 17:17:00 2017 +0100 app-crypt/eid-mw: add missing dep bug #608434. Vincent Hardy Thank you ! :) BTW you can ping me anytime. :)
