From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marius Bakke Subject: bug#36882: Qemu 4.2.0 build for x86_64-linux fails Date: Tue, 03 Mar 2020 21:26:24 +0100 Message-ID: <87v9nli3rj.fsf@devup.no> References: <87k14gnqng.fsf@gmail.com> <87mu9b3crd.fsf@gnu.org> <87a75a5taw.fsf@gmail.com> <87o8tptu7u.fsf@gnu.org> <87ftf0nx7n.fsf@gmail.com> <87tv3gm59r.fsf@gnu.org> <875zfuag6v.fsf@gmail.com> <874kveafns.fsf@gmail.com> <874kv6ju1c.fsf@devup.no> <878skh3n0o.fsf@gmail.com> <871rq9ejpb.fsf@gmail.com> 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]:44345) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j9E87-0000Sn-DQ for bug-guix@gnu.org; Tue, 03 Mar 2020 15:27:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1j9E86-0006Mi-Dx for bug-guix@gnu.org; Tue, 03 Mar 2020 15:27:03 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:34049) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1j9E86-0006Me-B7 for bug-guix@gnu.org; Tue, 03 Mar 2020 15:27:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1j9E86-0000F4-8U for bug-guix@gnu.org; Tue, 03 Mar 2020 15:27:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <871rq9ejpb.fsf@gmail.com> 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-mx.org@gnu.org Sender: "bug-Guix" To: Mathieu Othacehe Cc: 36882@debbugs.gnu.org --=-=-= Content-Type: text/plain Hello Mathieu & Ludo, (+ janneke) Mathieu Othacehe writes: >> Yup, turned out patching GCC was too difficult. I'm experimenting a >> filter over inputs passed to set-path-environment-variable in set-paths. > > This is also quite tricky, because the "libc" input passed to set-paths > must not be removed from C_INCLUDE_PATH in (gnu packages commencement) > for mes packages. If that is the only issue preventing us from solving this problem for all build systems, I'd say let's fix that. We could rename it obviously, though there are a few places that expect the "libc" key so it may become unwieldly. Can we find another way to detect the Mes toolchain, perhaps directly in gnu-build-system where we apply this workaround? E.g. look for inputs where (string-contains (package-name input) "mesboot")? Suggestions? --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAl5evXEACgkQoqBt8qM6 VPqS/gf8DTDN4gBernK/9GE0wTwo8eWR4/Y00zij+CkcArCMtElob5rsCw9L2gzo B1KrkAwc7RdVpX+Tf/vMLKEmeTsT6MODWk/ONWWViSRhSF4zYm4olYpMNwDBrRgt gY3hY2RdDJ8SD3vsyB4DDV+zhPs2s9Peghh/D3bcjoP1MYRtHyxKWN3tgDdc3yPr Re+Tszf1G4TfBK+6PHc2tMhIeR1Jbyfv9QAXpSjUOLSM+BUQWiSvorggFd8hFzFa Q/qClFvK+gW6iU/Ue37RW+GLWqD0v6Lp+lcT8HUsdastRw4YXNG/0kZEIUFD+yGg nInEAOrLdecXfP+Bu+YmIC7/7xuC5g== =7Ugt -----END PGP SIGNATURE----- --=-=-=--