From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marius Bakke Subject: bug#37593: [core-updates] Linux-Libre fails to build on aarch64-linux Date: Sun, 06 Oct 2019 18:13:12 +0200 Message-ID: <87a7ad7syv.fsf@devup.no> References: <877e5m98nv.fsf@devup.no> <87a7ain6j7.fsf@gmx.com> <87tv8n74f4.fsf@devup.no> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:57916) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iH9AZ-0003s7-Ph for bug-guix@gnu.org; Sun, 06 Oct 2019 12:14:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iH9AY-0007tQ-C5 for bug-guix@gnu.org; Sun, 06 Oct 2019 12:14:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:37917) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iH9AY-0007tK-8s for bug-guix@gnu.org; Sun, 06 Oct 2019 12:14:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iH9AY-0005tD-3x for bug-guix@gnu.org; Sun, 06 Oct 2019 12:14:02 -0400 Sender: "Debbugs-submit" Resent-To: bug-guix@gnu.org Resent-Message-ID: In-Reply-To: List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: =?UTF-8?Q?G=C3=A1bor?= Boskovits Cc: 37593-done@debbugs.gnu.org --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable G=C3=A1bor Boskovits writes: > Hello Marius, > > Marius Bakke ezt =C3=ADrta (id=C5=91pont: 2019. okt= . 5., Szo, > 14:40): > >> Pierre Langlois writes: >> >> > Hi Marius, >> > >> > Marius Bakke writes: >> > >> >> Berlin fails to build "linux-libre" for AArch64 on the 'core-updates' >> >> branch. Here is a recent attempt: >> >> >> >> https://ci.guix.gnu.org/build/1758844/details >> >> >> >> Log file for the latest build: >> >> >> >> >> https://ci.guix.gnu.org/log/aq2rnrmjsgnyk8vmsm7aa3mgdj39dcwh-linux-libre= -5.2.17.drv >> >> >> >> This seems to be the salient bit: >> >> >> >> CC [M] arch/arm64/lib/xor-neon.o >> >> In file included from >> /gnu/store/nr1aw4i32h7rmxwmq7d2da0mwcwg551j-glibc-2.29/include/stdint.h:= 34:0, >> >> from >> /gnu/store/yckkivhynk4hjcr0iry9vbcyc0lqqnxj-gcc-7.4.0-lib/lib/gcc/aarch6= 4-unknown-linux-gnu/7.4.0/include/arm_neon.h:33, >> >> from ./arch/arm64/include/asm/neon-intrinsics.h:33, >> >> from arch/arm64/lib/xor-neon.c:11: >> >> >> /gnu/store/nr1aw4i32h7rmxwmq7d2da0mwcwg551j-glibc-2.29/include/bits/stdi= nt-intn.h:27:19: >> error: conflicting types for 'int64_t' >> >> typedef __int64_t int64_t; >> >> ^~~~~~~ >> >> In file included from ./include/linux/list.h:5:0, >> >> from ./include/linux/module.h:9, >> >> from arch/arm64/lib/xor-neon.c:10: >> >> ./include/linux/types.h:114:15: note: previous declaration of 'int64_= t' >> was here >> >> typedef s64 int64_t; >> >> ^~~~~~~ >> >> In file included from >> /gnu/store/nr1aw4i32h7rmxwmq7d2da0mwcwg551j-glibc-2.29/include/stdint.h:= 37:0, >> >> from >> /gnu/store/yckkivhynk4hjcr0iry9vbcyc0lqqnxj-gcc-7.4.0-lib/lib/gcc/aarch6= 4-unknown-linux-gnu/7.4.0/include/arm_neon.h:33, >> >> from ./arch/arm64/include/asm/neon-intrinsics.h:33, >> >> from arch/arm64/lib/xor-neon.c:11: >> >> >> /gnu/store/nr1aw4i32h7rmxwmq7d2da0mwcwg551j-glibc-2.29/include/bits/stdi= nt-uintn.h:27:20: >> error: conflicting types for 'uint64_t' >> >> typedef __uint64_t uint64_t; >> >> ^~~~~~~~ >> >> In file included from ./include/linux/list.h:5:0, >> >> from ./include/linux/module.h:9, >> >> from arch/arm64/lib/xor-neon.c:10: >> >> ./include/linux/types.h:112:15: note: previous declaration of >> 'uint64_t' was here >> >> typedef u64 uint64_t; >> >> ^~~~~~~~ >> >> make[1]: *** [scripts/Makefile.build:285: arch/arm64/lib/xor-neon.o] >> Error 1 >> >> make: *** [Makefile:1073: arch/arm64/lib] Error 2 >> >> make: *** Waiting for unfinished jobs.... >> >> >> >> Not sure what's going on here. Ideas? >> > >> > Ha, that looks familiar, the same issue happened back in July: >> > https://lists.gnu.org/archive/html/guix-devel/2019-07/msg00175.html >> > >> > I don't think we worked out what was the problem exactly though :-/ >> >> So I was able to build it with this patch: >> >> >> It's not very pretty though. Thoughts? >> > > I believe that we encountered similar CPATH related problems earlier, whi= ch > were fixed by pathes like this, so it looks good to me. Maybe it would > worth investigating the pattern though, and create some generic mechanism > to deal with it. Wdyt? I don't think we've had to remove libc from CPATH before. We could do that in gnu-build-system if it becomes a pattern. A more general solution to the CPATH vs C_INCLUDE_PATH problem could be to present GCC a union of all the inputs as C_INCLUDE_PATH, because I suspect the main problem is having multiple entries in arbitrary order. Not sure if that would help this particular issue though. In any case I pushed the fix as c5ceec4150f6a6cdc1b64781afa2d05547cf8542. Thanks for the feedback! --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAl2aEpgACgkQoqBt8qM6 VPoPpQgAuSr3oyysVzHKTqAfwBeRFIE7tNmoud+drZK1e5O2Dt8t2qmzoa6GjIAf 0vzhPMydUjLHqYIw7MzxB3KbkaCOlPMaJC6ZLxzKwepH4DweIoUVGsan5nFW9sVx B8tz/J74DvN9dNfPaYUpzO4m7Boj1ay3Q+P0J9RTybZj68r7/kwEyR892hMmG7di CSdcrytBwzYSJ8XBlpHhtr9yc6T/itMaBRGSvpCmWmVmYgYK5AHmcCKYynRMiRfP o9Br9ka7MjSNHLUlkby64TxmTf9Z743Crio2nK0pVKlXkSaiglgDkNz7aMWzs50e nAdvFCPArOanA4gEbYWegbp8RjXfnw== =uA0L -----END PGP SIGNATURE----- --=-=-=--