unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Guillaume Le Vaillant <glv@posteo.net>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Cross compilation status
Date: Tue, 12 Sep 2023 15:05:35 +0000	[thread overview]
Message-ID: <87msxrbefu.fsf@kitej> (raw)
In-Reply-To: <87lede2xvu.fsf@gnu.org>

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

Mathieu Othacehe <othacehe@gnu.org> skribis:

> 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
>
> while the rest of the build-systems do accept cross-compiling packages:
>
> clojure, qt, copy, minetest-mod, tree-sitter, raw, linux-module, glib-or-gtk,
> asdf/source, go, cmake, minify, perl, trivial, guile, elm, font, gnu, asdf/ecl,
> asdf/sbcl, meson, mozilla, texlive

Hi.
I'm surprised to see asdf/* in the list of build systems accepting
to cross-compile packages. How did you test them?

Because I get (on a x86-64 machine):
--8<---------------cut here---------------start------------->8---
$ guix build --target=aarch64-linux-gnu sbcl-alexandria
guix build: error: gnu/packages/lisp-xyz.scm:168:2: sbcl-alexandria@1.4: build system `asdf/sbcl' does not support cross builds

$ guix build --target=aarch64-linux-gnu ecl-alexandria
guix build: error: gnu/packages/lisp-xyz.scm:168:2: ecl-alexandria@1.4: build system `asdf/ecl' does not support cross builds
--8<---------------cut here---------------end--------------->8---

I'm not even sure if sbcl and ecl have the ability to compile Common
Lisp code for an architecture different from the one they are running
on.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

      parent reply	other threads:[~2023-09-12 18:53 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
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 [this message]

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=87msxrbefu.fsf@kitej \
    --to=glv@posteo.net \
    --cc=guix-devel@gnu.org \
    --cc=othacehe@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).