The package seems to be building tests during "make all" phase even though I don't have FEATURES=test enabled. For details see my blog: http://blog.flameeyes.eu/articles/2008/06/11/please-dont-build-your-examples-by-default . It would be nice if the tests were disabled by default and only built with FEATURES=test. You can find an example patch usually suitable for upstream on the blog above. Thanks, Diego
Hi all, Here are two patches that fix the problem: - A patch for configure.ac and Makefile.am to add a new --enable-test option and use the result of the option to build or not build tests. - An update to media-libs/gd-2.0.35-r2 to apply the previous patch, run eautoreconf and use the new configure option. Tested on x86 with and without test feature. The patch on configure.ac and Makefile.am was not proposed upstream yet. I wait for feedback from Gentoo devs first. Didier
Created attachment 227269 [details, diff] media-libs/gd-2.0.35-r2 update
Created attachment 227271 [details, diff] patch for configure.ac and Makefile.am
7 months without any progress on this bug! Is the patch I proposed a bad one? Any feedback on it would be welcome...
Why not just replace "noinst_PROGRAMS" with "check_PROGRAMS" in Makefile.am? That way they'll only build when 'make check' is called.
(In reply to comment #5) > Why not just replace "noinst_PROGRAMS" with "check_PROGRAMS" in Makefile.am? > That way they'll only build when 'make check' is called. The tests that are built are as far as I know not automated tests, so I didn't think about the check target. Is it fine to use the check target to build binaries without running any test with them?
*** Bug 226289 has been marked as a duplicate of this bug. ***
seems like it was fixed by this commit: http://sources.gentoo.org/media-libs/gd/gd-2.0.35-r3.ebuild?r1=1.1&r2=1.2