From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: bug#27489: glibc fails to build on i686 Date: Wed, 28 Jun 2017 22:52:57 -0400 Message-ID: <20170629025257.GA16840@jasmine.lan> References: <87podrlvsb.fsf@elephly.net> <87tw2zk3uk.fsf@openmailbox.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="LZvS9be/3tNcYl/X" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:57769) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dQPap-0006QG-AD for bug-guix@gnu.org; Wed, 28 Jun 2017 22:54:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dQPal-0001k5-Dj for bug-guix@gnu.org; Wed, 28 Jun 2017 22:54:07 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:40555) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dQPal-0001j7-0t for bug-guix@gnu.org; Wed, 28 Jun 2017 22:54:03 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dQPak-0000dQ-Ix for bug-guix@gnu.org; Wed, 28 Jun 2017 22:54:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: <87tw2zk3uk.fsf@openmailbox.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: Adonay Felipe Nogueira Cc: 27489@debbugs.gnu.org --LZvS9be/3tNcYl/X Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jun 28, 2017 at 09:57:39PM -0300, Adonay Felipe Nogueira wrote: > Here is my situation: >=20 > - I'm using Guix in a foreign distribution (Trisquel 7). >=20 > - In 2017-06-12, I pulled and upgraded Guix and packages successfully as > root. >=20 > - Last weekend I did (all as root): `guix gc` (successful), `guix pull` > (successful), `guix package -u guix` (not successful, because of this > bug). I'm sorry you experienced this bug. We didn't test the change to glibc on i686-linux so we didn't notice this problem until after we pushed it. > - Some time has passed, and the core-updates branch now seems to have a > fix for this bug. As announced earlier in this bug discussion, the bug was fixed on the master branch with commit ffc015bea26f24d862e7e877d907fbe1ab9a9967. https://git.savannah.gnu.org/cgit/guix.git/commit/?id=3Dffc015bea26f24d862e= 7e877d907fbe1ab9a9967 > - Yesterday (or was it the day before it?), I did (all as root): `guix > gc` (successful), `guix pull` (not successfull, because of this bug), > `guix gc`, `guix pull > --url=3D"https://git.savannah.gnu.org/cgit/guix.git/snapshot/guix-ed068= b960eeedb92823238783779730319b8ba0e.tar.gz"` > (not successful, because of this bug). Notice that in the last pull I > used the snapshot corresponding to the merge in core-updates that has > the fix. I recommend you try again, but on the master branch. Core-updates is not currently usable (hopefully soon!). --LZvS9be/3tNcYl/X Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAllUa4YACgkQJkb6MLrK fwhjOg/9F1fAQbH8FELz/q6JNmMP3VM0KXD7pc26TvmdeJC5VAem6BDqgW9+R63v FHQKeCbwieh18kGcIuSAJ16G/wWrf2enU9A9mADmJEpXz+I3qGsXNy1YS4Y4UpDn FWZVfVJ2HlX4u0+4TGomLePNxwNYCWoPUQK4X+JpRm+kYGtjf7N46zcwlSDW75KY Fxu5BbcTCNh0mkfWbfx62xhPdeE8I2h8UeBWDapkp3Bqtw7+ioOYMXBpZJC0YXDW dS1O8DApbF7Kyu0mty8lWe+Mrngn4V7EqLr6ykQQG0RwtOxoAZwNLFrLoItCp0Bo oK0JTuasTsEOoBT8pZOFPwg5gelO/4X9cqCOSPdg1E3r1PnN0Rw7Q34ad8ROYHrM 3PCa9g5IDUrR8Uijsceg9PTGNAtZ4sCZjwm+snfPDnx0yKuG3HTynh80k3VTkLcj p+jxnRCj/OpPO03972kXHjKOUkfRzWp3X2Hy+S993cuPhEWxRyc/zd1hYZJhEhKJ U2K52biZm01yQbV7bgiBG2OxTvri+r0fdFWcCwrZpIqB6J8139xiXKm5ocRCaagr f0AAoDoXwvSq1sZViPPgb9OKjFa/zeTEXvq/1F0tR/EwOKe1BkTifU0CD37O14x4 5JAJOevFzTcch19wuyM4CTjEQrM59U/xXp9alV8IBKXzDZrXhDo= =nnag -----END PGP SIGNATURE----- --LZvS9be/3tNcYl/X--