From: ludo@gnu.org (Ludovic Courtès)
To: Eli Zaretskii <eliz@gnu.org>
Cc: wingo@pobox.com, guix-devel@gnu.org, guile-user@gnu.org
Subject: Re: guix is the guildhall that we always wanted!
Date: Sat, 18 Mar 2017 15:04:52 +0100 [thread overview]
Message-ID: <87bmsy65q3.fsf@gnu.org> (raw)
In-Reply-To: <83d1dgyr5e.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 17 Mar 2017 15:22:21 +0200")
Hi Eli,
Eli Zaretskii <eliz@gnu.org> skribis:
>> From: ludo@gnu.org (Ludovic Courtès)
>> Date: Fri, 17 Mar 2017 12:30:57 +0100
>> Cc: guix-devel@gnu.org, guile-user@gnu.org
>>
>> > Open questions would be, what about other targets like macOS or Windows
>> > or whatever? There I don't know. I suspect that if Guix becomes
>> > popular enough, someone will make a thing whereby you can cross-compile
>> > to macOS from GNU/Linux at least. I know you can do that already with
>> > MinGW. As for native "guildhall" operation on these targets, I don't
>> > know. But I think that is a cost that people will pay for in time.
>>
>> We could surely create cross-compiled packs for MinGW, though I suspect
>> a number of packages do not support cross-compilation.
>
> The MinGW build doesn't support multithreading in Guile, so any such
> cross-compiled packages should be aware of that. Also, there are some
> Posix functionality not supported, like primitive-fork, so if Guix
> uses that, those parts won't work.
The goal is not to run Guix on MinGW.
I think Andy was referring to the possibility of cross-compiling
packages that use Guile to MinGW. That is already possible thanks to
the work of Jan Jan Nieuwenhuizen, and since yesterday, we can create
“packs” that contain binaries cross-compiled for MinGW:
https://lists.gnu.org/archive/html/guix-devel/2017-03/msg00525.html
Ludo’.
next prev parent reply other threads:[~2017-03-18 14:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 18:25 guix is the guildhall that we always wanted! Andy Wingo
2017-03-16 19:26 ` Amirouche Boubekki
2017-03-17 8:23 ` Andy Wingo
2017-03-18 0:10 ` Arne Babenhauserheide
2017-03-16 22:01 ` Mark H Weaver
2017-03-16 22:24 ` Ludovic Courtès
2017-03-17 9:01 ` Florian Paul Schmidt
2017-03-17 9:45 ` Andy Wingo
2017-03-17 11:24 ` Ludovic Courtès
2017-03-17 6:51 ` Marko Rauhamaa
2017-03-17 8:30 ` Andy Wingo
2017-03-17 13:54 ` Christopher Allan Webber
2017-03-17 14:26 ` Andy Wingo
2017-03-18 14:00 ` Ludovic Courtès
2017-03-17 11:30 ` Ludovic Courtès
2017-03-17 12:32 ` Andy Wingo
2017-03-17 17:39 ` Pjotr Prins
2017-03-17 18:16 ` Mike Gran
2017-03-17 13:22 ` Eli Zaretskii
2017-03-18 14:04 ` Ludovic Courtès [this message]
2017-03-18 14:10 ` Eli Zaretskii
2017-03-19 15:57 ` Ludovic Courtès
2017-03-19 16:22 ` Eli Zaretskii
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=87bmsy65q3.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=eliz@gnu.org \
--cc=guile-user@gnu.org \
--cc=guix-devel@gnu.org \
--cc=wingo@pobox.com \
/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).