unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
To: David Pirotte <david@altosw.be>
Cc: guile-user <guile-user@gnu.org>, guile-devel <guile-devel@gnu.org>
Subject: Re: G-Golf- [subject changed] cairo based examples fail in homebrew
Date: Fri, 22 Dec 2023 15:55:01 -0800	[thread overview]
Message-ID: <CA+XASoWEdT6JDoo+p+VJ7nPDk+01T0Vd9LxwrtvGN4U22fD=Ew@mail.gmail.com> (raw)
In-Reply-To: <20231222202214.3489cf55@tintin>

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

On Fri, Dec 22, 2023 at 3:22 PM David Pirotte <david@altosw.be> wrote:

> Hi Aleix,
>
>         i decided to answer separately - and  change the subject line -
>         (a) the guile-cairo related issue, on homebrew, from the
>

Just to be clear, there's no issue with guile-cairo I believe. The segfault
with guile-cairo was when using Guile's upstream.


>         (b) snapshot related issue, on homebrew as well
>
>         here is the 'subthread' for the guile-cairo related issue, on
>         homebrew [1].
>
> > > > Anyways, guile-cairo is fine going back to stable 3.0.9.
>
> > > Ok, so just to make sure, now both the gtk4/simple-paintable.scm and
> > > gtk4/animated-paintable.scm examples work fine on 'your' platform as
> > > well?
>
> > Nope, they don't. Sorry, I should have been much more explicit and
> > provide more info.
>
> Ok - These are two examples ported from the upstream gtk4-demo, can you
> run one or both of these examples? [screenshot attached of the upstream
> gt4-demo ui (on debian trixie (current testing)).
>
> If they don't work, please report upstream, if they do work, try to get
> a backtrace as well, for the simple-animation.scm example only, let's
> try to identify the problem for the simplest one ...
>
>
Ah nice, I didn't know that. They work well, see screenshot. The animated
one is the same but rotating the nuclear icon.

This is a good clue though, at least we know where not to look.

Aleix

[-- Attachment #2: Screenshot 2023-12-22 at 3.50.35 PM.png --]
[-- Type: image/png, Size: 113290 bytes --]

  parent reply	other threads:[~2023-12-22 23:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-02  3:50 GNU G-Golf 0.8.0-rc-2 available for testing David Pirotte
2023-12-01 17:51 ` Aleix Conchillo Flaqué
2023-12-02  0:10   ` David Pirotte
2023-12-04  4:15     ` Aleix Conchillo Flaqué
2023-12-04  4:16       ` Aleix Conchillo Flaqué
2023-12-05  4:21         ` David Pirotte
2023-12-05  4:14       ` David Pirotte
2023-12-09 20:49         ` Aleix Conchillo Flaqué
2023-12-21  8:44         ` Aleix Conchillo Flaqué
2023-12-22  4:52           ` David Pirotte
2023-12-22  7:01             ` Aleix Conchillo Flaqué
2023-12-22  7:34               ` Aleix Conchillo Flaqué
2023-12-22 23:22               ` G-Golf- [subject changed] cairo based examples fail in homebrew David Pirotte
2023-12-22 23:43                 ` David Pirotte
2023-12-22 23:55                 ` Aleix Conchillo Flaqué [this message]
2024-01-01  2:12                   ` 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='CA+XASoWEdT6JDoo+p+VJ7nPDk+01T0Vd9LxwrtvGN4U22fD=Ew@mail.gmail.com' \
    --to=aconchillo@gmail.com \
    --cc=david@altosw.be \
    --cc=guile-devel@gnu.org \
    --cc=guile-user@gnu.org \
    /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).