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

[Ludovic Courtès]

John Darrington <address@hidden> skribis:

> On Sat, Dec 14, 2013 at 07:19:03PM +0100, Ludovic Courtès wrote:
>      John Darrington <address@hidden> 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.

Yeah, perhaps we could add that when cross building (we have only two
occurrences currently, but it may be needed quite often.)

>      > *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.

Oh indeed, I was unaware of that.  So that explains why libgpg-error
must be passed both as a native and target input.

However, is --with-gpg-error-prefix really needed?  By default the cross
gcc will find the target libgpg-error in its search path, and not the
native one, so I would guess this is OK.

Thanks,
Ludo’.