From: Efraim Flashner <efraim@flashner.co.il>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>,
andrew@trop.in, bjoern.hoefling@bjoernhoefling.de,
guix@cbaines.net, 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 12:20:41 +0300 [thread overview]
Message-ID: <ZP2KaSjsdqQ3wNcR@pbp> (raw)
In-Reply-To: <87lede2xvu.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 907 bytes --]
On Sun, Sep 10, 2023 at 11:14:29AM +0200, Mathieu Othacehe wrote:
>
> I have CC'ed members of the python, java, ruby, rust, r, haskell and
> emacs teams. Any plans adding cross-compilation support to your
> build-system, barriers to overcome?
Speaking as the one who added the rakudo build system and the perl6
packages, IMO all the perl6 packages should be removed and also the
rakudo-build-system. I don't believe most of the packages have built for
more than a year and I don't believe they have ever had any adoption. If
it turns out that Raku (no longer perl6 for several years now) would
make use of the current rakudo-build-system then we can always revert
removing it.
--
Efraim Flashner <efraim@flashner.co.il> רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-09-10 9:21 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 [this message]
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
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=ZP2KaSjsdqQ3wNcR@pbp \
--to=efraim@flashner.co.il \
--cc=andrew@trop.in \
--cc=bjoern.hoefling@bjoernhoefling.de \
--cc=cox.katherine.e+guix@gmail.com \
--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).