From: Efraim Flashner <efraim@flashner.co.il>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: Mathieu Othacehe <othacehe@gnu.org>,
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, rekado@elephly.net,
jgart@dismail.de
Subject: Re: Cross compilation status
Date: Mon, 18 Sep 2023 17:17:51 +0300 [thread overview]
Message-ID: <ZQhcD8oFhapTj6gx@3900XT> (raw)
In-Reply-To: <14e0b7bb9eab77527257769507aa4a42d72a5f83.camel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1333 bytes --]
On Sun, Sep 10, 2023 at 04:59:35PM +0200, Liliana Marie Prikler wrote:
> Hi Mathieu,
>
> Am Sonntag, dem 10.09.2023 um 11:14 +0200 schrieb Mathieu Othacehe:
> > 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?
> For Emacs, there are layers of problems. First things first, we are
> only doing byte compilation atm, which may or may not be arch-dependant
> based on stuff like endianness. For native compilation, there is the
> thing that even a slightly differently configured emacs won't load the
> packages you've just compiled without compiling it natively on its own.
> Granted, if we want to do cross-compilation, having just the bytecode
> might already be "good enough", but I wanted to throw this out there.
>
> I think we'd need some support from Emacs proper before we can start
> implementing cross builds.
I will note that the only big-endian architecture which we "support" is
32-bit powerpc, so we don't have to worry that much about wrong
endianness.
--
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-18 14:18 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZQhcD8oFhapTj6gx@3900XT \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.