From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: Re: The reason why gst-libav is broken on x86_64 Date: Mon, 22 Jun 2015 10:13:56 -0400 Message-ID: <878ubbj0ez.fsf@netris.org> References: <87mvzt87jc.fsf@netris.org> <87zj3sw4y8.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:45011) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z72UG-0006oW-0G for guix-devel@gnu.org; Mon, 22 Jun 2015 10:14:13 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z72UA-0004cY-Iz for guix-devel@gnu.org; Mon, 22 Jun 2015 10:14:11 -0400 In-Reply-To: <87zj3sw4y8.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 22 Jun 2015 09:57:35 +0200") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: guix-devel@gnu.org ludo@gnu.org (Ludovic Court=C3=A8s) writes: > Mark H Weaver skribis: > >> FYI, I investigated the problem with gst-libav on x86_64, and it turns >> out that it began when we updated nettle from 2.7 to 3.1, the latter of >> which is configured with --enable-fat. For details, see my post on >> bug-nettle: >> >> http://lists.lysator.liu.se/pipermail/nettle-bugs/2015/003389.html > > Interesting, thanks for investigating. Followup at > . > >> We could work around the problem by removing the --enable-fat configure >> option, although it will entail a lot of rebuilding. While we're at it, >> we should also update to nettle-3.1.1. > > If we don=E2=80=99t use --enable-fat, then we get non portable binaries, > don=E2=80=99t we? Maybe it's not enough to simply remove --enable-fat, but presumably there's a way to compile a non-fat nettle that targets a machine with the minimum set of required features for a given target. Anyway, a better option would be to simply disable the IFUNC method of initializing nettle. > Would it work to use nettle-2.7 for instance for gst-libav? No, nettle is getting linked into gst-libav via several levels of indirection. One way is via the path: gst-libav -> ffmpeg -> libquvi -> curl -> gnutls -> nettle Maybe there are other paths as well, I don't know. Anyway, if we were to introduce nettle-2.7 back into the mix, then we'd surely end up with two different versions of nettle being linked into the same program, which caused problems for us some time ago as I recall. Mark