unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: John Darrington <john@darrington.wattle.id.au>
To: Ludovic Court??s <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 2/5] gnu: gnupg: Fixed cross-compile issues.
Date: Sun, 15 Dec 2013 09:24:28 +0100	[thread overview]
Message-ID: <20131215082427.GA5093@intra> (raw)
In-Reply-To: <8761qrta62.fsf@gnu.org>

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

On Sat, Dec 14, 2013 at 10:06:13PM +0100, Ludovic Court??s wrote:
     John Darrington <john@darrington.wattle.id.au> skribis:
     
     > 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.
     
     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 #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2013-12-15  8:30 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-14 17:43 [PATCH 1/5] gnu: libxml2: Fixed cross-compilation John Darrington
2013-12-14 17:43 ` [PATCH 2/5] gnu: gnupg: Fixed cross-compile issues John Darrington
2013-12-14 18:19   ` Ludovic Courtès
2013-12-14 19:02     ` John Darrington
2013-12-14 21:06       ` Ludovic Courtès
2013-12-15  8:24         ` John Darrington [this message]
2013-12-15  8:39           ` [PATCH] gnu: gnupg: Fix " John Darrington
2013-12-15 21:24             ` Ludovic Courtès
2013-12-15 21:14           ` [PATCH 2/5] gnu: gnupg: Fixed " Ludovic Courtès
2014-01-07 10:32         ` John Darrington
2013-12-14 17:43 ` [PATCH 3/5] gnu: tzdata: Added "source" as input John Darrington
2013-12-14 18:24   ` Ludovic Courtès
2013-12-14 17:43 ` [PATCH 4/5] gnu: openssl: Fixed cross-compile issues John Darrington
2013-12-14 17:57   ` Ludovic Courtès
2013-12-14 18:02     ` John Darrington
2013-12-14 21:01       ` Ludovic Courtès
2013-12-15  8:03         ` [PATCH] gnu: openssl: Fix " John Darrington
2013-12-15 21:18           ` Ludovic Courtès
2013-12-14 17:43 ` [PATCH 5/5] gnu: Changed many "inputs" which should be "native-inputs" John Darrington
2013-12-14 21:48   ` Ludovic Courtès
2013-12-15 10:36     ` John Darrington
2013-12-15 11:01       ` [PATCH] gnu: Move numerous " John Darrington
2013-12-15 21:32         ` Ludovic Courtès
2013-12-14 17:48 ` [PATCH 1/5] gnu: libxml2: Fixed cross-compilation Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20131215082427.GA5093@intra \
    --to=john@darrington.wattle.id.au \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).