Thanks Julián, Julián Moreno Patiño <jul...@debian.org> writes:
> Package: openrc > Version: 0.12.4+20131230-9 > Severity: serious > > openrc 0.12.4+20131230-9 FTBFS on armel,armhf and ppc64el: > https://buildd.debian.org/status/package.php?p=openrc > > * Checking hidden functions in librc.so ... * Checking trailing > whitespace in code ... [ ok ] > * Checking trailing newlines in code ... [ ok ] > * Checking for obsolete functions ... [ ok ] > * Checking for x* func usage ... [ ok ] > * Checking spacing style ... [ ok ] > * Running unit tests > * is_older_than ... [ ok ] > make[3]: *** [test] Error 1 > make[2]: *** [test] Error 2 > make[1]: *** [test] Error 2 > dh_auto_test: make -j1 test returned exit code 2 > make[3]: Leaving directory `/«BUILDDIR»/openrc-0.12.4+20131230/src/test' > make[2]: Leaving directory `/«BUILDDIR»/openrc-0.12.4+20131230/src' > make[1]: Leaving directory `/«BUILDDIR»/openrc-0.12.4+20131230' > make: *** [build-arch] Error 2 Interesting. Gentoo has OpenRC well tested for arm(hf,el,eb) and ppc(32,64). http://packages.gentoo.org/package/sys-apps/openrc I guess the build system could not recognize keywords like armel, armhf or ppc64el. Hmm, it fails with the unit tests, could be the loop solver also. Thomas, do you have time to take a look? I don't have an account for the porterboxes. Best, Benda
