From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marius Bakke Subject: bug#35232: webkitgtk-2.24.1 fails to build on i686, but earlier versions work Date: Tue, 16 Apr 2019 23:45:32 +0200 Message-ID: <875zrdvd37.fsf@fastmail.com> References: <874l74sdyk.fsf@netris.org> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:40900) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hGVtz-0001Vk-LU for bug-guix@gnu.org; Tue, 16 Apr 2019 17:46:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hGVty-0003Nj-HZ for bug-guix@gnu.org; Tue, 16 Apr 2019 17:46:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:53305) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hGVty-0003Na-9s for bug-guix@gnu.org; Tue, 16 Apr 2019 17:46:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hGVty-0006Nu-4i for bug-guix@gnu.org; Tue, 16 Apr 2019 17:46:02 -0400 Sender: "Debbugs-submit" Resent-To: bug-guix@gnu.org Resent-Message-ID: In-Reply-To: <874l74sdyk.fsf@netris.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.org@gnu.org Sender: "bug-Guix" To: Mark H Weaver , 35232-done@debbugs.gnu.org --=-=-= Content-Type: text/plain Mark H Weaver writes: > Hydra failed to build webkitgtk-2.24.1 on i686-linux, saying "SSE2 > support is required to compile WebKit". > > https://hydra.gnu.org/build/3439652 > > See below for the tail of the build log. Note that earlier versions of > webkitgtk built successfully on i686-linux, including 2.24.0: > > https://hydra.gnu.org/job/gnu/master/webkitgtk-2.24.0.i686-linux > > Removing support for i686, or even for systems without SSE2, seems like > an odd thing for upstream to do in a point release. Is it truly the > case, or can we fix this with a change in configuration? I dug around in the upstream git SVN mirror and found that the the (harmless) change causing this failure had been reverted. Fixed in commit e28ff04108ae7, thanks for reporting it! --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAly2TP0ACgkQoqBt8qM6 VPqyMQf/Y/81k/pbMQlgmuavKX2imjgdbCDHxLDuwPV3+wxZQV6mr9PMO6fmTWDo z4K4dI5AdnbdhqVLo1Jx5ZDdoO8L0Mr68iBK8me5OFaiZbRIM7nPGILAdBrxOINb bTbz1UQ4Jig24m0YLK4SGVCZXvxpWw75TgEqI/4457zARM4oKMMugxlWKZ8LGmRe Chz32rgd8n6YlNtXj4A8iKdZce6xlpmhjs9ty3ro4hC8JWtG1fTZaXS8I8dKdjFK RlvHnxQt8OdNDU5EmeX3bvJ5TMB32NfRUhp9mZ+IcN7+ZmZ6N6rIdlCc3k4zW+xc Q7wMRrx0FHbR0KTXooHvksujGhDTrw== =9S9L -----END PGP SIGNATURE----- --=-=-=--