unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mathieu Othacehe <m.othacehe@gmail.com>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel@gnu.org
Subject: Re: How can I set architecture/system-specific origin sources?
Date: Tue, 31 Dec 2019 13:06:36 +0100	[thread overview]
Message-ID: <87eewksnqr.fsf@gmail.com> (raw)
In-Reply-To: <87imlwd96p.fsf@ambrevar.xyz>


Hello Pierre,

>
> My laptop is a x86_64-linux and the above definition always uses the
> x86_64 source, even with
>
>   guix build --system=i686-linux foo
>
> In Nix, the following works:
>
> --8<---------------cut here---------------start------------->8---
>   src =
>     if stdenv.hostPlatform.system == "x86_64-linux" then
>       fetchurl {
>         url = "http://foo.bar/...";
>         sha256 = "e8ff01e6cc38d1b3fd56a083f5860737dbd2f319a39037528fb1a74a89ae9878";
>       }
>     else if stdenv.hostPlatform.system == "i686-linux" then
>       fetchurl {
>         url = "http://foo.bar/...";
>         sha256 = "cef3591e436f528852db0e8c145d3842f920e0c89bcfb219c466797cb7b18879";
>       }
>     else throw "foo does not support platform ${stdenv.hostPlatform.system}";
> --8<---------------cut here---------------end--------------->8---
>
> Is this a Guix bug?

Well, it's not really a bug, but quite suprising at first. If you look
at the definition of <package> in (guix packages), you'll see that some
fields are (thunked). %current-system and %current-target-system will
only return valid results in (thunked) fields.

As "source" is not thunked, you can make it thunked, but it can hurt
performances. You can also make multiple packages for each architecture,
and use them as inputs conditionned by %current-system and
%current-target-system.

Mathieu

  reply	other threads:[~2019-12-31 12:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-31 11:30 How can I set architecture/system-specific origin sources? Pierre Neidhardt
2019-12-31 12:06 ` Mathieu Othacehe [this message]
2019-12-31 14:00   ` Pierre Neidhardt
2020-01-01 12:22     ` Efraim Flashner
2020-01-02 11:21       ` Pierre Neidhardt
2020-01-02 22:16   ` Ludovic Courtès
2020-01-02 22:33     ` Pierre Neidhardt

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=87eewksnqr.fsf@gmail.com \
    --to=m.othacehe@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=mail@ambrevar.xyz \
    /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).