unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>,
	 andrew@trop.in, bjoern.hoefling@bjoernhoefling.de,
	 guix@cbaines.net, efraim@flashner.co.il,  julien@lepiller.eu,
	cox.katherine.e+guix@gmail.com,  lars@6xq.net,
	liliana.prikler@gmail.com,  rekado@elephly.net,
	 jgart@dismail.de
Subject: Re: Cross compilation status
Date: Sun, 10 Sep 2023 08:55:47 -0400	[thread overview]
Message-ID: <87zg1uuqzw.fsf@gmail.com> (raw)
In-Reply-To: <87lede2xvu.fsf@gnu.org> (Mathieu Othacehe's message of "Sun, 10 Sep 2023 11:14:29 +0200")

Hi Mathieu!

Mathieu Othacehe <othacehe@gnu.org> writes:

> Hello,
>
> In order for Guix to become an alternative to tools such as Yocto and
> Buildroot, having most or all our packages cross-compiling is a
> prerequisite.
>
> Here is a status of cross-compilation in Guix. For cross-compilation to
> work, the build-system needs to support cross-compilation.
>
> The following build-systems explicitly refuse cross-compiling packages:
>
> haskell, agda, waf, chicken, rakudo, julia, python, emacs, rebar,
> cargo, ruby, renpy, dub, android-ndk, scons, dune, ant, pyproject,
> maven, asdf, r, ocaml, node

For Python, it's already reported at: https://issues.guix.gnu.org/60733.
And even implemented here: https://issues.guix.gnu.org/60849.

Why it hasn't been merged yet is because it's coupled with a more daring
change (unified build system for Python) and there were comments that
this should be an all or nothing change, so I'd need to workout all the
build systems and see what breakage happens at the global scale, which
is a rather large undertaking.

Maybe it could be decoupled from that change and tested in isolation,
pushed first; we'd loose the benefit of the later change which is the
ability to avoid wrapping native-inputs in our wrappers.

-- 
Thanks,
Maxim


  parent reply	other threads:[~2023-09-10 12:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-10  9:14 Cross compilation status Mathieu Othacehe
2023-09-10  9:20 ` Efraim Flashner
2023-09-10  9:27 ` Efraim Flashner
2023-09-10 12:55 ` Maxim Cournoyer [this message]
2023-09-10 14:59 ` Liliana Marie Prikler
2023-09-18 14:17   ` Efraim Flashner
2023-09-18 17:01     ` Liliana Marie Prikler
2023-09-11 16:19 ` Simon Tournier
2023-09-11 17:10   ` Liliana Marie Prikler
2023-09-12 15:05 ` Guillaume Le Vaillant

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=87zg1uuqzw.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=andrew@trop.in \
    --cc=bjoern.hoefling@bjoernhoefling.de \
    --cc=cox.katherine.e+guix@gmail.com \
    --cc=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    --cc=guix@cbaines.net \
    --cc=jgart@dismail.de \
    --cc=julien@lepiller.eu \
    --cc=lars@6xq.net \
    --cc=liliana.prikler@gmail.com \
    --cc=othacehe@gnu.org \
    --cc=rekado@elephly.net \
    /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).