Re: [PATCH 2/5] gnu: gnupg: Fixed cross-compile issues.

[John Darrington <john@darrington.wattle.id.au>]

[-- Attachment #1: Type: text/plain, Size: 1422 bytes --]

On Sat, Dec 14, 2013 at 07:19:03PM +0100, Ludovic Courtès wrote:
     John Darrington <john@darrington.wattle.id.au> skribis:
     
     > *gnu/packages/gnupg.scm (libgpg-error): Added gcc as a native input,
     >  and set the CC_FOR_BUILD variable.
     
     The implicit inputs when cross-compiling include both the cross-gcc and
     the native gcc (see build-system/gnu.scm.)
     
     AFAICS setting CC_FOR_BUILD=gcc should be enough (it uses ‘cc’ by
     default.)  Can you confirm.

You are right.  setting gcc as a native input seems to be unnecessary.  Somewhat on
a tangent:
  Would it not be a good idea to have CC_FOR_BUILD=gcc the default setting 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.
     
     This is wrong: libgcrypt would end up linking against the native libgpg-error.

I think you are mistaken.  The purpose of --with-gpg-error-prefix= is to set the path
of the library which it should be linked against.  The issue is, that libgpg-error provides
both a binary (which must be run at configure time) AND a library which has to be linked.

J'



-- 
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]