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: Wed, 26 Feb 2020 22:12:39 +0100 Message-ID: <87lfop2gu0.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> 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]:51846) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j73zL-0005Wj-SG for bug-guix@gnu.org; Wed, 26 Feb 2020 16:13:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1j73zK-0000Mm-BR for bug-guix@gnu.org; Wed, 26 Feb 2020 16:13:03 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:51868) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1j73zK-0000L7-7q for bug-guix@gnu.org; Wed, 26 Feb 2020 16:13:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1j73zK-0000ad-0N for bug-guix@gnu.org; Wed, 26 Feb 2020 16:13:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87tv3gm59r.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: > Incidentally, do we have problems building anything other than QEMU? The only other regression I've noticed with the C_INCLUDE_PATH change is that GHC 8.4 fails to build -- previously we at least got to GHC 8.6. The error message does not make much sense to me (something about libffi.so not found), but it must be related to the C_INCLUDE_PATH change since it built before. So I think we can work around these problems for now and try to fix it properly in the next core-updates cycle (rumor has it that it includes a switch to GCC 9 as well). --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAl5W30cACgkQoqBt8qM6 VPp3PQf/XOd8yaCvxWYdqhcNc6qT+OFrwfjFvny5ySuuQxnOgkhK2n9G0x2VdFdy ODng4eqrhig5hsAoUOxDhIWCSofLeyl2Up6X2C8Xd35R2x4PGlHo9cwstQ56fv/v iZdkVLaHq4FrpCavXsPZo+vmaDruXMNIiD3Qsz8/1kIZHcfvh9UQ5l0vsWMxl2tI gvKXvf2TL3XGVZfMGFLwmv94TShO9iyN6UyVTc+aNLf7fux1GCPz35wXIzSWc7Tf DJVAucjBKiuAjsxk6qOZiu65jHRBYK63qd19nA3GbCpJF9KltMOCMNOZ7QQZSnQJ CXC/ctgDAN86EP7G+b1xNZkuUbIXpQ== =12Bl -----END PGP SIGNATURE----- --=-=-=--