On 9 May 2010 08:05, Adam D. Barratt <a...@adam-barratt.org.uk> wrote:
> On Sun, May 9, 2010 01:05, Dmitrijs Ledkovs wrote:
>> On 9 May 2010 00:44, Adam D. Barratt <a...@adam-barratt.org.uk> wrote:
>>> - waf's parallel building and hppa don't mix; I've stolen a patch which
>>> Jakub Wilk provided for xmms2 and applied it to j-a-c-k. It will break
>>> anything causes the .waf.-* directory to be renamed, but that seems like
>>> another reason not to use waf ;-)
>> Running waf with "-j1" flag should stop all paralelism.
>> ./waf configure build -j1
>> Is this not enough to make waf behave on hppa?
> From what I could see from reading the code, the number of jobs should
> automatically default to the number of available CPUs in any case, so
> should automatically be 1 at least on the porter box.
> However, assuming that adding the following to debian/rules would
> implement your suggestion, then sadly no it does not appear to be enough:
> waf-configure-options += $(if $(filter hppa,$(DEB_HOST_ARCH)),-j1)
> Even with this change, the "./waf configure" call hangs after outputting
> Checking for dbus-1 >= 1.0.0 : ok
> Checking for dbus-1 flags : ok
> Checking for header expat.h : ok
> I killed it after 15 minutes of inactivity; the build output shows that
> -j1 was passed to the configure call. If I add the Runner.py patch
> instead, it gets past that point with ease (and later fails with the
> second error I mentioned, which is trivially fixable by adding "&&
> !defined(__hppa__)" to an existing patch).
Can you please run it as (without any patches)
./waf -vvv -j1
And send me buildlog please? This is quite disturbing. I'm a waf lover
=) and have submitted a few patches upstream.
pkg-multimedia-maintainers mailing list