From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: bug#29113: Warnings when starting vim: Relink with for IFUNC symbol `longjmp' Date: Mon, 25 Feb 2019 22:18:48 -0500 Message-ID: <20190226031848.GA6982@jasmine.lan> References: <20171102051501.37coaia27mrpb5xg@lang> <87po8ap3h4.fsf@fastmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="7JfCtLOvnd9MIVvH" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:42135) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gyTHn-0000JP-Pi for bug-guix@gnu.org; Mon, 25 Feb 2019 22:20:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gyTHn-0000RP-02 for bug-guix@gnu.org; Mon, 25 Feb 2019 22:20:03 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:38564) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gyTHm-0000RC-RN for bug-guix@gnu.org; Mon, 25 Feb 2019 22:20:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gyTHm-00075I-JK for bug-guix@gnu.org; Mon, 25 Feb 2019 22:20:02 -0500 Sender: "Debbugs-submit" Resent-To: bug-guix@gnu.org Resent-Message-ID: Content-Disposition: inline In-Reply-To: <87po8ap3h4.fsf@fastmail.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.org@gnu.org Sender: "bug-Guix" Cc: 29113-done@debbugs.gnu.org --7JfCtLOvnd9MIVvH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 22, 2017 at 07:34:15PM +0100, Marius Bakke wrote: > This is a known problem in glibc that has recently been fixed AFAICT. >=20 > https://sourceware.org/bugzilla/show_bug.cgi?id=3D21041 >=20 > It was also "backported" to the 2.26 release branch: >=20 > https://sourceware.org/git/?p=3Dglibc.git;a=3Dcommit;h=3D88758c4ad3f046d0= 50bc2c3ae0f172b6524ca6c2 >=20 > We currently have 2.26 in 'core-updates' which hasn't started building > yet. Perhaps we should include this fix, thoughts? Now we are using 2.28 and I can't reproduce the problem, so I'm closing the bug. --7JfCtLOvnd9MIVvH Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAlx0sBEACgkQJkb6MLrK fwhlfw/9E89PEjulBwTpsPrcnUXrLd4jvL5KC3gP6yjeXDJ1/ZJNJjmN2hFWTl3m 1aJr5TjiclQttP2blV+fWStsROYYCKP4AOn6YmBc405c+4bgYwqz3AEzQsmh72X/ RyA6HrQUe9IvFc1QFqTTonB8Z/F2tzRgRgRy4qCL22VXoL+HsrAj/SkYi1Neqxjh qCfhFGu4PFSHgTHrUu11KZroz+vopRxBUaa/FXSLUTdSYjjR7Knoa4yH+VfkxyBJ 94s9IUHGOfh26xWqZStLY7TUsrk6i4anDponPwUXJhoaSl2wcnXxBnNrO5+18og0 MJu2jvhBMAtFI6wcdO6ht/JJn4AEt2p9lgz+49ji2xTcIqOADYakI20x+9WnRR2m kqXnYLA77/p6SLQ2N6kRaHqndXm1yh2VO5Cst0tQ01WD+JfAdMBl7YtDgsNdWy2/ ovOE2GHPXnjxPvzPKUtoa1nxc8tjUBwvVafVvBW14lHF0lfS4fJQZtGDzsx2rC+/ Ob1qL1TnQ3X8kOJzzbf0eKRSUtlKenysA2mN8khYF81AF1qjJlDE8nQ3hqrjPXQi 3jRzL5+cuZCI0cQzW9JVTn0czj36zdeNshN4rTJXo24VpJ8XxbO/YlEhtG3cA51a oNDW4akx76j13I95JIur8A/ol5jiNRwPn2nES6uBP/zdgc67yrs= =ghFt -----END PGP SIGNATURE----- --7JfCtLOvnd9MIVvH--