guix-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: John Darrington
Subject: Re: [PATCH 2/5] gnu: gnupg: Fixed cross-compile issues.
Date: Sun, 15 Dec 2013 09:24:28 +0100
User-agent: Mutt/1.5.21 (2010-09-15)

On Sat, Dec 14, 2013 at 10:06:13PM +0100, Ludovic Court??s wrote:
     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.)

Pspp should have CC_FOR_BUILD set, but doesn't currently.
     
     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.
     

Without --with-gpg-error-prefix I get the following error when cross compiling:

libtool: link: mips64el-linux-gnu-gcc -shared  -fPIC -DPIC  
.libs/libgcrypt_la-visibility.o .libs/libgcrypt_la-misc.o 
.libs/libgcrypt_la-global.o .libs/libgcrypt_la-sexp.o 
.libs/libgcrypt_la-hwfeatures.o .libs/libgcrypt_la-stdmem.o 
.libs/libgcrypt_la-secmem.o .libs/libgcrypt_la-missing-string.o 
.libs/libgcrypt_la-module.o .libs/libgcrypt_la-fips.o 
.libs/libgcrypt_la-hmac256.o .libs/libgcrypt_la-ath.o  -Wl,--whole-archive 
../cipher/.libs/libcipher.a ../random/.libs/librandom.a ../mpi/.libs/libmpi.a 
../compat/.libs/libcompat.a -Wl,--no-whole-archive  -Wl,-rpath 
-Wl,/nix/store/c3crv7mdmbc5sib7vznf0183n5xxa8kv-libgpg-error-1.12/lib 
-Wl,-rpath 
-Wl,/nix/store/c3crv7mdmbc5sib7vznf0183n5xxa8kv-libgpg-error-1.12/lib 
-L/nix/store/c3crv7mdmbc5sib7vznf0183n5xxa8kv-libgpg-error-1.12/lib 
/nix/store/c3crv7mdmbc5sib7vznf0183n5xxa8kv-libgpg-error-1.12/lib/libgpg-error.so
  -O2 -Wl,--version-script=./libgcrypt.vers   -Wl,-soname -Wl,libgcrypt.so.11 
-o .libs/libgcrypt.so.11.8.2
/nix/store/c3crv7mdmbc5sib7vznf0183n5xxa8kv-libgpg-error-1.12/lib/libgpg-error.so:
 could not read symbols: File in wrong format
collect2: error: ld returned 1 exit status
Makefile:493: recipe for target 'libgcrypt.la' failed
make[2]: *** [libgcrypt.la] Error 1

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: signature.asc
Description: Digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]