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: Thu, 05 Mar 2020 17:42:06 +0100 Message-ID: <87a74ulpnl.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> <87v9ni92tf.fsf@gnu.org> 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]:33053) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j9taQ-0006u7-VC for bug-guix@gnu.org; Thu, 05 Mar 2020 11:43:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1j9taP-00052t-Uo for bug-guix@gnu.org; Thu, 05 Mar 2020 11:43:02 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:37663) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1j9taP-00052E-Qg for bug-guix@gnu.org; Thu, 05 Mar 2020 11:43:01 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1j9taP-0008SS-OV for bug-guix@gnu.org; Thu, 05 Mar 2020 11:43:01 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87v9ni92tf.fsf@gnu.org> 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: Ludovic =?UTF-8?Q?Court=C3=A8s?= , Mathieu Othacehe Cc: 36882@debbugs.gnu.org --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Ludovic Court=C3=A8s writes: > Hi! > > Mathieu Othacehe skribis: > >>> 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. > > Yeah, fiddling with =E2=80=98set-paths=E2=80=99 sounds like opening a can= of worms. > >> So, maybe the best option is to patch QEMU directly, as proposed in >> the attached patch. WDYT? > > I=E2=80=99m all in favor of that for now. It=E2=80=99s likely that QEMU = is the only > package having problems, as Marius noted (the GHC error sounds like it > could be something different), so I=E2=80=99d say go for the package-spec= ific > solution for now. Indeed, I will push Mathieus commit shortly. clang-runtime requires a similar fix for CPLUS_INCLUDE_PATH. No idea what's up with GHC@8.4 yet, but unsurprisingly removing libc from the include paths does not make a difference. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAl5hK94ACgkQoqBt8qM6 VPo5Ngf9HaMvlMVCEZrjWjszDD6IikU5UuEGu9MZWVD+qXBW4IVnj12vKbnadEwa Isb14pi5h58xGoEwow02lvES+sWV3ejguc8D+PsAHaPXGLA0fX5uWaARf+YuAoYt MJQeHAFZa8CvkBWykFphLVyeNUnYIGB9mPVum8JNjWOUTfbuXDHpzSHpfqdU6CDa M61XWQjD8/QEI0kAE7LPbLVxlwRIhlnEs43AQmcCvwCfIoB0fq0aitRLha5DUD3g WyTosvi1OE3ys1RUmz3ILq28MKe8PiIIvOgqaG2eAAzxVvccP+3fCfRha/e8fpM4 JH7vJrGVzTAGYyxL+JfYmtvX45FQeA== =wXXd -----END PGP SIGNATURE----- --=-=-=--