unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: Andy Wingo <wingo@igalia.com>,
	19180@debbugs.gnu.org, guile-devel@gnu.org
Subject: bug#19180: Weak tables harmful to GC?
Date: Mon, 30 Oct 2017 23:18:51 +0100	[thread overview]
Message-ID: <87d154wa7o.fsf__28392.2140290544$1509401964$gmane$org@gnu.org> (raw)
In-Reply-To: <878tfslfgl.fsf@mdc-berlin.de> (Ricardo Wurmus's message of "Mon,  30 Oct 2017 18:20:58 +0100")

Hi,

Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> skribis:

> previously I wrote:
>
>> The “guile-awesome” package finished compiling (after about 46 minutes).
>> I’m now testing “guix pull” with a version of Guix that uses
>> “guile-awesome”.
>
> I’m sure I’m doing something wrong (see below for guesses).  Here’s what
> I get:
>
> ./pre-inst-env guix pull
> loading...       26.0% of 645 filesrandom seed for tests: 1509382171
> compiling...     18.9% of 645 filesIn thread:
> ERROR: In procedure return: return used outside of 'with-monad'Error while printing exception.
> compiling...     54.7% of 645 files^C

The error above is the other bug you reported, not related (but just as
serious): <https://bugs.gnu.org/27476>.

> I modified build-self.scm to use the modified Guile:
>
> diff --git a/build-aux/build-self.scm b/build-aux/build-self.scm
> index ed8ff5f..9af6504 100644
> --- a/build-aux/build-self.scm
> +++ b/build-aux/build-self.scm
> @@ -126,7 +126,7 @@ running Guile."
>    (package->derivation (cond-expand
>                           (guile-2.2
>                            (canonical-package
> -                           (specification->package "guile@2.2")))
> +                           (specification->package "guile-awesome@2.2")))
>                           (else
>                            (canonical-package
>                             (specification->package "guile@2.0"))))))
>
> I also confirmed that the Guile process that is spawned as “bin/guile
> --no-auto-compile /home/rwurmus/guix/scripts/guix pull” is indeed the
> modified Guile, but I noticed that it spawns yet another Guile process
> to load and compile Guix.
>
> I guess that comes from the daemon?  If that’s the case I can’t really
> test this on this big server, because the daemon is currently in use, so
> I can’t just reconfigure it to use the modified Guile.

Your patch above should have led to the use of “guile-awesome” to
compile Guix; I’m not sure why it didn’t.

> When compiling Guix from source with “make -j 32” using that version of
> Guile I got a segfault.

Oh?

Let’s put this on hold since Andy offers a different solution.

Thanks for testing!

Ludo’.





  parent reply	other threads:[~2017-10-30 22:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87wp9gwz8m.fsf@gnu.org>
     [not found] ` <87fug4o8z2.fsf@pobox.com>
     [not found]   ` <87wp54z3p5.fsf@gnu.org>
     [not found]     ` <87zi9th1i6.fsf_-_@gnu.org>
     [not found]       ` <87y3o454pr.fsf@gnu.org>
     [not found]         ` <87r2tvncs5.fsf@dustycloud.org>
     [not found]           ` <87wp3mwwef.fsf@gnu.org>
     [not found]             ` <87po9c88rx.fsf@dustycloud.org>
     [not found]               ` <87o9owm9v1.fsf@gnu.org>
2017-10-25  0:50                 ` bug#19180: Weak tables harmful to GC? Christopher Allan Webber
     [not found]                 ` <87o9ow830m.fsf@dustycloud.org>
2017-10-25 17:11                   ` Ludovic Courtès
     [not found]             ` <87mv4gd0ik.fsf@elephly.net>
2017-10-25  6:38               ` Ricardo Wurmus
2017-10-26  7:03               ` Ludovic Courtès
     [not found]               ` <87a80eie63.fsf@gnu.org>
2017-10-26  8:35                 ` Ricardo Wurmus
     [not found]                 ` <87k1zimhmt.fsf@elephly.net>
2017-10-26 16:52                   ` Ricardo Wurmus
2017-10-26 17:17                   ` Ludovic Courtès
     [not found]                   ` <87bmktn96e.fsf@elephly.net>
2017-10-27  5:28                     ` Ludovic Courtès
     [not found]                     ` <87tvyl9n22.fsf@gnu.org>
2017-10-28  9:56                       ` Ricardo Wurmus
     [not found]                       ` <87r2tnlhno.fsf@elephly.net>
2017-10-30 12:35                         ` Ludovic Courtès
     [not found]                         ` <87a8087qz7.fsf@gnu.org>
2017-10-30 14:48                           ` Ricardo Wurmus
     [not found]                           ` <87d154lmio.fsf@mdc-berlin.de>
2017-10-30 17:20                             ` Ricardo Wurmus
     [not found]                             ` <878tfslfgl.fsf@mdc-berlin.de>
2017-10-30 22:18                               ` Ludovic Courtès [this message]
2017-10-30 17:29                           ` Andy Wingo
2017-10-30 23:13                             ` Ludovic Courtès
     [not found]                             ` <87zi88ut3k.fsf@gnu.org>
2017-10-31  8:25                               ` Andy Wingo
     [not found]                               ` <877evbiuzy.fsf@igalia.com>
2017-10-31 16:56                                 ` Ludovic Courtès

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://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='87d154wa7o.fsf__28392.2140290544$1509401964$gmane$org@gnu.org' \
    --to=ludo@gnu.org \
    --cc=19180@debbugs.gnu.org \
    --cc=guile-devel@gnu.org \
    --cc=ricardo.wurmus@mdc-berlin.de \
    --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.
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).