From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Darrington Subject: Re: [PATCH 2/5] gnu: gnupg: Fixed cross-compile issues. Date: Sat, 14 Dec 2013 20:02:18 +0100 Message-ID: <20131214190218.GA8061@intra> References: <1387043002-6138-1-git-send-email-john@darrington.wattle.id.au> <1387043002-6138-2-git-send-email-john@darrington.wattle.id.au> <87y53nthwo.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vkogqOf2sHV7VnPd" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40511) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VruTr-0004Ak-6O for guix-devel@gnu.org; Sat, 14 Dec 2013 14:02:31 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VruTm-00041e-WA for guix-devel@gnu.org; Sat, 14 Dec 2013 14:02:27 -0500 Content-Disposition: inline In-Reply-To: <87y53nthwo.fsf@gnu.org> 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 =?iso-8859-1?Q?Court=E8s?= Cc: guix-devel@gnu.org --vkogqOf2sHV7VnPd Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Dec 14, 2013 at 07:19:03PM +0100, Ludovic Court=C3=A8s wrote: John Darrington skribis: =20 > *gnu/packages/gnupg.scm (libgpg-error): Added gcc as a native input, > and set the CC_FOR_BUILD variable. =20 The implicit inputs when cross-compiling include both the cross-gcc and the native gcc (see build-system/gnu.scm.) =20 AFAICS setting CC_FOR_BUILD=3Dgcc should be enough (it uses =E2=80=98c= c=E2=80=99 by default.) Can you confirm. You are right. setting gcc as a native input seems to be unnecessary. Som= ewhat on a tangent: Would it not be a good idea to have CC_FOR_BUILD=3Dgcc the default settin= g at least fot the gnu build-system. > *gnu/packages/gnupg.scm (libgcrypt): Added libgpg-error as a native = input and > set the --with-gpg-error-prefix configure option. =20 This is wrong: libgcrypt would end up linking against the native libgp= g-error. I think you are mistaken. The purpose of --with-gpg-error-prefix=3D is to = set the path of the library which it should be linked against. The issue is, that libgp= g-error provides both a binary (which must be run at configure time) AND a library which has= to be linked. J' --=20 PGP Public key ID: 1024D/2DE827B3=20 fingerprint =3D 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3 See http://sks-keyservers.net or any PGP keyserver for public key. --vkogqOf2sHV7VnPd Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlKsqzkACgkQimdxnC3oJ7PjuACdFfx5axqAHbQ5jjK/jvHIFTNq BGgAn00bBYUjZSbDo+e3SUIIFtp9yJJu =PwQF -----END PGP SIGNATURE----- --vkogqOf2sHV7VnPd--