From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Jordan Subject: Re: Freezing core-updates Date: Tue, 17 May 2016 08:03:24 -0400 Message-ID: <87twhwyjqr.fsf@mailerver.i-did-not-set--mail-host-address--so-tickle-me> References: <87h9dxukjm.fsf@gnu.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]:44098) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b2djp-0002OK-4p for guix-devel@gnu.org; Tue, 17 May 2016 08:04:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b2djj-0008P8-5v for guix-devel@gnu.org; Tue, 17 May 2016 08:04:36 -0400 Received: from forward18o.cmail.yandex.net ([2a02:6b8:0:1a72::1e8]:51412) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b2djh-0008LA-Qc for guix-devel@gnu.org; Tue, 17 May 2016 08:04:31 -0400 In-reply-to: <87h9dxukjm.fsf@gnu.org> 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" To: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: Guix-devel Hi Ludovic Court=C3=A8s, Just to clear does this mean any new package submissions are now be put o= n hold? Respectfully, --=20 Matthew Jordan Sent with my mu4e Ludovic Court=C3=A8s writes: > Hello Guix! > > I hereby declare =E2=80=98core-updates=E2=80=99 frozen! :-) > > That is, we should now work towards fixing the =E2=80=9Ccore=E2=80=9D p= ackages, then make > Hydra build everything, fix packages, and finally merge it. I invite > you all to spend a bit of time on it, it=E2=80=99s fun and profitable. = :-) > > Currently, the main problem is a frightening GCC 5.3 build issue on ARM= : > : > > --8<---------------cut here---------------start------------->8--- > make[3]: Leaving directory '/tmp/nix-build-gcc-5.3.0.drv-0/build' > Comparing stages 2 and 3 > warning: gcc/cc1plus-checksum.o differs > warning: gcc/cc1-checksum.o differs > Bootstrap comparison failure! > gcc/fold-const.o differs > gcc/cp/semantics.o differs > gcc/cp/optimize.o differs > gcc/dwarf2cfi.o differs > gcc/tree-ssa-sccvn.o differs > gcc/real.o differs > gcc/libgcov-driver-tool.o differs > gcc/tree-nested.o differs > gcc/lto-section-out.o differs > gcc/c/c-typeck.o differs > gcc/c/c-parser.o differs > gcc/lto-streamer-out.o differs > gcc/tree-dfa.o differs > gcc/ipa-inline.o differs > gcc/c-family/cilk.o differs > gcc/gcov-dump.o differs > gcc/coverage.o differs > gcc/tree-inline.o differs > gcc/omp-low.o differs > gcc/double-int.o differs > gcc/tree-ssa-math-opts.o differs > gcc/simplify-rtx.o differs > gcc/df-scan.o differs > gcc/tree-switch-conversion.o differs > libiberty/fibheap.o differs > libiberty/simple-object-xcoff.o differs > libiberty/sort.o differs > libiberty/pic/fibheap.o differs > libiberty/pic/simple-object-xcoff.o differs > libiberty/pic/sort.o differs > Makefile:21400: recipe for target 'compare' failed > make[2]: *** [compare] Error 1 > --8<---------------cut here---------------end--------------->8--- > > Can someone with an ARM machine reproduce it? I wonder if it could be = a > hardware failure. > > See for more. > > Ludo=E2=80=99.