all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Andy Wingo <wingo@igalia.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Building Guix with Guile 2.1
Date: Sat, 24 Sep 2016 12:31:05 +0900	[thread overview]
Message-ID: <87y42irn2e.fsf@gnu.org> (raw)
In-Reply-To: <874m59fan7.fsf@igalia.com> (Andy Wingo's message of "Wed, 21 Sep 2016 19:03:24 +0200")

Hi!

Andy Wingo <wingo@igalia.com> skribis:

> On Wed 21 Sep 2016 10:23, ludo@gnu.org (Ludovic Courtès) writes:
>
>> Hello!
>>
>> Nalaginrut reported that Guix fails to build with Guile 2.2, which was a
>> bit of a shame, hence commits e465d9e19087ab150f7e31f21c09e4a147b93b36
>> and 9d126aa2b504bb9fad536eac186805ff623e96be.
>>
>> Now, the hack in build-aux/compile-all.scm doesn’t quite work with 2.2,
>> and it was already quite fragile.
>
> Which hack?  You mean loading modules before compiling?  I guess you
> should load the compiler modules too FWIW, perhaps that's an issue.
>
> If there is a nice change we can do to make module-loading thread-safe,
> let's think about that :)  It's probably the biggest thread-safety
> problem we have in Guile and now would be the right time to fix it.

I agree this is the right thing to do.

My guess is that this would have to be approached in C, to avoid the fat
mutex overhead.  But hmm, I dunno exactly what this entails!

Ludo’.

  parent reply	other threads:[~2016-09-24  5:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-21  8:23 Building Guix with Guile 2.1 Ludovic Courtès
2016-09-21 17:03 ` Andy Wingo
2016-09-21 19:40   ` Taylan Ulrich Bayırlı/Kammer
2016-09-21 19:48     ` Taylan Ulrich Bayırlı/Kammer
2016-09-24  3:31   ` Ludovic Courtès [this message]
2016-09-21 21:01 ` Taylan Ulrich Bayırlı/Kammer
2016-09-22  9:22   ` Andy Wingo
2016-09-22 20:45     ` Taylan Ulrich Bayırlı/Kammer
2016-09-30 11:51       ` Ludovic Courtès
2016-09-27  9:48   ` Ludovic Courtès
2016-09-28 14:56     ` Taylan Ulrich Bayırlı/Kammer
2016-09-28 15:14       ` Andy Wingo
2016-09-29 22:02         ` Taylan Ulrich Bayırlı/Kammer

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=87y42irn2e.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=wingo@igalia.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 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.