Created attachment 349832 [details] emerge --info On my hardened ~amd64 machine with gcc-4.8.0 I see the following error when running the test suite of gegl. TEST: /bin/sh... /bin/sh: (pid=5048) --quiet: invalid option Usage: /bin/sh [GNU long option] [option] ... /bin/sh [GNU long option] [option] script-file ... GNU long options: --debug --debugger --dump-po-strings --dump-strings --help --init-file --login --noediting --noprofile --norc --posix --protected --rcfile --restricted --verbose --version Shell options: -irsD or -c command or -O shopt_option (invocation only) -abefhkmnptuvxBCHP or -o option FAIL: /bin/sh TEST: ../../test-driver... (pid=5050) ../../test-driver: invalid option: '--quiet' Usage: test-driver --test-name=NAME --log-file=PATH --trs-file=PATH [--expect-failure={yes|no}] [--color-tests={yes|no}] [--enable-hard-errors={yes|no}] [--] TEST-SCRIPT The '--test-name', '--log-file' and '--trs-file' options are mandatory. FAIL: ../../test-driver
Created attachment 349834 [details] build log
The same happens for me with media-libs/gegl-0.2.0-r2.
Created attachment 358952 [details, diff] gegl-0.2.0-r2.ebuild.patch I've looked into this, and it's because the test/xml directory uses the gtester program from glib to run it's tests, using the automake TESTS_ENVIRONMENT variable - the command-line looks like (simplified): gtester ./test-save # etc However, the current version of automake in Gentoo (1.13.4 on my machine; the gegl tarball was prepared with 1.11.3) apparently wraps the test files in its own driver script, making it look like (again, simplified): gtester /bin/sh test-driver [bunch of options] ./test-save Unfortunately gtester doesn't support this usage, as it assumes each of its arguments is a separate test program, so it fails miserably. Therefore the simplest fix would be to add WANT_AUTOMAKE=1.11 to the ebuild, as in the attached patch.
+ 01 Oct 2013; Sebastian Pipping <sping@gentoo.org> gegl-0.2.0-r1.ebuild, + gegl-0.2.0-r2.ebuild: + Fix tests (bug #471990), thanks to David Leverton! +
Isn't there another fix for building with > 1.11 ? For example, for me it build with 1.14 fine. This is 1/3 last packages depending on 1.11 (at least on my system).
