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, John Darrington <jmd@gnu.org>
Subject: Re: [PATCH] gnu: fix some issues cross-compiling glib
Date: Wed, 19 Nov 2014 11:07:52 +0100	[thread overview]
Message-ID: <20141119100752.GA16625@jocasta.intra> (raw)
In-Reply-To: <874mtv3723.fsf@gnu.org>

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

On Wed, Nov 19, 2014 at 09:53:24AM +0100, Ludovic Court??s wrote:
     
     You probably need (assoc-ref (or native-inputs inputs) "bash"), meaning
     you???ll refer to the native Bash both when compiling natively and when
     cross-compiling (as done in ATLAS and OpenSSL.)

OK, I will try that.
     
     core-updates no longer exists.  Perhaps let???s just make a
     ???cross-compilation??? branch (or ???arm????) with all such changes.
     Then we???ll arrange for Hydra to build that branch, and merge it once
     it???s stable and mostly built.
     
     WDYT?

Ok.  Had you in mind to have this branch natively compiled for Arm, or cross-compiled?

If the former, then obviously the necessary hardware will be needed.  If the latter,
then there are still some obstacles to overcome before it'll work.

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:[~2014-11-19 10:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-18 10:34 [PATCH] gnu: fix some issues cross-compiling glib John Darrington
2014-11-18 20:36 ` Ludovic Courtès
2014-11-18 20:54   ` John Darrington
2014-11-19  8:53     ` Ludovic Courtès
2014-11-19 10:07       ` John Darrington [this message]
2014-11-19 12:47         ` 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=20141119100752.GA16625@jocasta.intra \
    --to=john@darrington.wattle.id.au \
    --cc=guix-devel@gnu.org \
    --cc=jmd@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).