Anyone up to debugging apr (again?)
Hi,
there’s one failure with apr at the moment. I don’t remember
exactly if Mikael fixed this one or something else already…
(there seem to have been more errors than just one, when I
last noticed it), but if someone is up to some fixing, have fun.
bye,
//mirabilos
--
„Also irgendwie hast du IMMER recht. Hier zuckelte gerade ein Triebwagen mit
der Aufschrift "Ostdeutsche Eisenbahn" durch Wuppertal. Ich glaubs machmal
nicht…“ -- Natureshadow, per SMS
„Hilf mir mal grad beim Denken“ -- Natureshadow, IRL, 2x
---------- Forwarded message ----------
From: Stefan Fritsch <sf@debian.org>
Message-ID: <3908390.zh0eBFRKG3@k>
X-Spam-Status: No, hits=0.000000 required=0.900000
To: Thorsten Glaser <tg@mirbsd.de>
Date: Sat, 23 Nov 2013 23:05:04 +0100
Subject: Re: Log for attempted build of apr_1.4.8-3 on m68k (dist=unstable)
Am Samstag, 23. November 2013, 15:42:12 schrieben Sie:
> fail
>
> Failed Tests Total Fail Failed %
> ===================================================
> testshm 6 1 16.67%
Past experience (e.g. with hppa) tells me that apr test failures are
usually issues with kernel/glibc/toolchain on that architecture.
Please understand that I don't want to spend my time debugging these
components on a dead architecture. If you want, I can make failure of
this test non-fatal on m68k, though.
Cheers,
Stefan
Reply to: