unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Lee Thomas <leet22303be@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: tsyesika@tsyesika.se, 57379@debbugs.gnu.org, david@altosw.be
Subject: bug#57379: GUI toolkit for Guile 3.0?
Date: Tue, 30 Aug 2022 11:24:00 -0700	[thread overview]
Message-ID: <CANYin9WiGBOm8_hqbUrWzMZznngmeEJgLq8N0N-Rnd4Zi5QrTg@mail.gmail.com> (raw)
In-Reply-To: <87pmgivn3c.fsf@elephly.net>

[-- Attachment #1: Type: text/plain, Size: 930 bytes --]

I can confirm that disabling grafts allows both of the g-golf examples to
run, and they come up quickly. I suspect they were slow due to something
in the grafts; I'll find out. I still get some errors, but they also appear
to be related to guix. I'll read the discussion.

Thank you, Ricardo!

On Mon, Aug 29, 2022 at 12:58 PM Ricardo Wurmus <rekado@elephly.net> wrote:

>
> David Pirotte <david@altosw.be> writes:
>
> > I hope Ricardo, possibly with the help of other guix contributor's will
> > find a solution so that g-golf may also run 'out of the box' on guix.
>
> Turns out that it all works fine when you disable grafts:
>
>   guix shell --pure --no-grafts \
>     guile guile-g-golf gtk@4
>
> This echoes a discussion here:
>
>   https://github.com/spk121/guile-gi/issues/96
>
> The immediate lessons from the observations detailed in this issue are
> also why guile-gi works without disabling grafts.
>
> --
> Ricardo
>

[-- Attachment #2: Type: text/html, Size: 1481 bytes --]

  reply	other threads:[~2022-08-30 18:24 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-24  2:35 bug#57379: GUI toolkit for Guile 3.0? Lee Thomas
2022-08-24 12:29 ` Jessica Tallon
2022-08-24 16:05   ` Lee Thomas
2022-08-24 18:55     ` Jessica Tallon
2022-08-24 20:03   ` David Pirotte
2022-08-24 21:49     ` Lee Thomas
2022-08-26  2:27       ` David Pirotte
2022-08-26 20:03         ` Lee Thomas
2022-08-26 20:35           ` Ricardo Wurmus
2022-08-26 21:11             ` Lee Thomas
2022-08-27  8:30               ` Ricardo Wurmus
2022-08-28 23:04                 ` David Pirotte
2022-08-28 22:42           ` David Pirotte
2022-08-29  2:32             ` Lee Thomas
2022-08-29  9:11               ` Ricardo Wurmus
2022-08-29  9:12               ` Ricardo Wurmus
2022-08-29 16:54               ` David Pirotte
2022-08-29 18:22                 ` Lee Thomas
2022-08-29 23:23                   ` David Pirotte
2022-08-30 18:33                     ` Lee Thomas
2022-09-01  7:17                       ` adriano
2022-09-03  4:26                       ` David Pirotte
2022-08-29 19:55                 ` Ricardo Wurmus
2022-08-30 18:24                   ` Lee Thomas [this message]
2022-09-03  4:15                     ` David Pirotte

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=CANYin9WiGBOm8_hqbUrWzMZznngmeEJgLq8N0N-Rnd4Zi5QrTg@mail.gmail.com \
    --to=leet22303be@gmail.com \
    --cc=57379@debbugs.gnu.org \
    --cc=david@altosw.be \
    --cc=rekado@elephly.net \
    --cc=tsyesika@tsyesika.se \
    /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).