d4x-2.5.0_rc2 fails on ~x86 and ~sparc while building with the following; if g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/pango-1.0 -I/usr/X11R6/include -I/usr/include/freetype2 -include ../../config.h -mcpu=ultrasparc -mtune=ultrasparc -O2 -pipe -MT about.o -MD -MP -MF ".deps/about.Tpo" \ -c -o about.o `test -f 'about.cc' || echo './'`about.cc; \ then mv -f ".deps/about.Tpo" ".deps/about.Po"; \ else rm -f ".deps/about.Tpo"; exit 1; \ fi about.cc: In function `void init_about_window(...)': about.cc:220: error: `gtk_timeout_add' undeclared (first use this function) about.cc:220: error: (Each undeclared identifier is reported only once for each function it appears in.) make[3]: *** [about.o] Error 1 make[3]: Leaving directory `/var/tmp/portage/d4x-2.5.0_rc2/work/d4x-2.5.0rc2/main/face' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/d4x-2.5.0_rc2/work/d4x-2.5.0rc2/main' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/d4x-2.5.0_rc2/work/d4x-2.5.0rc2' make: *** [all] Error 2 !!! ERROR: net-misc/d4x-2.5.0_rc2 failed. !!! Function src_compile, Line 57, Exitcode 2 !!! (no error message) From what I can tell, this is not useflag related.
i think it has to do with gtk+-2.4 which is stable now
patch applied to 2.5.0_rc2. can sparc go and mark 2.5.0_rc2 for ~sparc?
Solution for me atleast: 1. Download d4x 2.5.0-rc3 from http://www.krasu.ru/soft/chuchelo/files/d4x-2.5.0rc3.tar.gz and copy it /usr/portage/distfiles 2. Get the ebuild and put it in an overlay directory (/usr/local/portage seems to be the default in /etc/make.conf. Put this ebuild in a folder /usr/local/portage/net-misc/d4x) 3. Get the patch and place in the file section of where the ebuild is (/usr/local/portage/net-misc/d4x/files) 4. ACCEPT_KEYWORDS=~x86 emerge d4x 5. Wait
Created attachment 30332 [details] The latest d4x ebuild
Created attachment 30333 [details, diff] The latest d4x ebuild patch
_rc4 in portage, should solve this bug