From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: Re: Fwd: [curl] Re: configure: --with-libidn or --with-libidn2? Date: Mon, 26 Dec 2016 14:19:16 +0000 Message-ID: <8760m6lqmz.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> References: <87bmvylrk5.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:48524) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cLW7F-0000em-6Z for guix-devel@gnu.org; Mon, 26 Dec 2016 09:19:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cLW7C-0004vC-2s for guix-devel@gnu.org; Mon, 26 Dec 2016 09:19:05 -0500 Received: from aibo.runbox.com ([91.220.196.211]:44607) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cLW7B-0004uX-SG for guix-devel@gnu.org; Mon, 26 Dec 2016 09:19:02 -0500 Received: from [10.9.9.210] (helo=mailfront10.runbox.com) by bars.runbox.com with esmtp (Exim 4.71) (envelope-from ) id 1cLW79-0006nF-8p for guix-devel@gnu.org; Mon, 26 Dec 2016 15:18:59 +0100 Received: from [46.29.248.238] (helo=localhost) by mailfront10.runbox.com with esmtpsa (uid:892961 ) (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) id 1cLW75-0006Jv-1X for guix-devel@gnu.org; Mon, 26 Dec 2016 15:18:55 +0100 In-Reply-To: <87bmvylrk5.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> 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" To: guix-devel@gnu.org ng0 writes: > It seems as if curl can be build with libidn2 now and they have > addressed the bug which existed for a while. I will check with > upstream and send in a fix for our curl package once I am sure > that the old bug has been fixed. Misinterpretation on my side, and I forgot that I'm read-only on that list. Is anyone up to date on libidn2 vs libidn, is version 2 now beyond the stage where it does not break anymore on unicode? > -- > ♥Ⓐ ng0 > PGP keys and more: https://n0is.noblogs.org/ http://ng0.chaosnet.org > > > Date: Thu, 01 Jan 1970 00:00:00 +0000 > > On Sat, 24 Dec 2016, Christian Weisgerber wrote: > MIME-Version: 1.0 > Content-Type: text/plain > >> In 7.51.0 and later, the actual configure script option for libidn2 >> is still "--with-libidn", but the help text refers to "--with-libidn2". > >> This can be fixed either way, but the inconsistency is confusing. > > Oops, yes that seems silly. I think we should switch to --with-libidn2 > completely. I'll fix! > > -- > > / daniel.haxx.se > ------------------------------------------------------------------- > List admin: https://cool.haxx.se/list/listinfo/curl-library > Etiquette: https://curl.haxx.se/mail/etiquette.html -- ♥Ⓐ ng0 PGP keys and more: https://n0is.noblogs.org/ http://ng0.chaosnet.org