unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Ludovic Courtès" <ludo@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 16:10:45 +0200	[thread overview]
Message-ID: <83bmsyy8t6.fsf@gnu.org> (raw)
In-Reply-To: <87bmsy65q3.fsf@gnu.org> (ludo@gnu.org)

> From: ludo@gnu.org (Ludovic Courtès)
> Cc: wingo@pobox.com,  guix-devel@gnu.org,  guile-user@gnu.org
> Date: Sat, 18 Mar 2017 15:04:52 +0100
> 
> 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

I'm saying that when cross-compiling, it's easy to produce binaries
that are unusable on Windows because Guile is not run natively during
the build, and so problems inherent to the Windows port are not
revealed during the build.  Multithreading is one such issue, quite a
significant one.  Unless I disable multithreading, I cannot build
Guile natively, because every non-trivial Guile program crashes (I
reported that years ago, but no one was able to explain why that
happens or point me to a workaround).

So if the above binaries include threads, I'm afraid they might not be
very useful on Windows.

  reply	other threads:[~2017-03-18 14:11 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
2017-03-18 14:10       ` Eli Zaretskii [this message]
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=83bmsyy8t6.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=guile-user@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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).