From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: Important libffi bug fix for MIPS N32 Date: Sat, 26 Oct 2013 22:41:17 +0200 Message-ID: <87sivnhij6.fsf@gnu.org> References: <871u3jmfkp.fsf@netris.org> <87wql4zi3t.fsf@netris.org> <87wql4a5nc.fsf@karetnikov.org> <87ob6gzdj4.fsf@netris.org> <87li1k2b5z.fsf@karetnikov.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33078) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VaAfk-0002Jr-6R for guix-devel@gnu.org; Sat, 26 Oct 2013 16:41:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VaAff-00028Y-3p for guix-devel@gnu.org; Sat, 26 Oct 2013 16:41:24 -0400 Received: from mail3-relais-sop.national.inria.fr ([192.134.164.104]:34939) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VaAfe-00028L-Td for guix-devel@gnu.org; Sat, 26 Oct 2013 16:41:19 -0400 In-Reply-To: <87li1k2b5z.fsf@karetnikov.org> (Nikita Karetnikov's message of "Wed, 23 Oct 2013 20:40:24 +0400") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Nikita Karetnikov Cc: guix-devel@gnu.org Nikita Karetnikov skribis: > (Not sure why my previous messages weren=E2=80=99t signed.) > >>> Now, should I test the mentioned fix? > >> Yes, please do! > > The coreutils package fails to build: > > FAIL: test-fchownat (exit: 134) > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D > > test-chown.h:193: assertion failed This line is: --8<---------------cut here---------------start------------->8--- ASSERT (st1.st_ctime < st2.st_ctime || (st1.st_ctime =3D=3D st2.st_ctime && get_stat_ctime_ns (&st1) < get_stat_ctime_ns (&st2))); --8<---------------cut here---------------end--------------->8--- (See .) Could it have something to do with nanosecond-resolution timestamp support in the kernel that=E2=80=99s running, or in the underlying file sys= tem? Ludo=E2=80=99.