unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: David Pirotte <david@altosw.be>
To: Matija Obid <matija.obid@posteo.net>
Cc: guile-user@gnu.org
Subject: Re: G-Golf - Callback segmentation fault
Date: Mon, 2 Sep 2024 18:18:54 -0300	[thread overview]
Message-ID: <20240902181854.2017f1fc@tintin> (raw)
In-Reply-To: <87cylo8xc4.fsf@posteo.net>

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

Hello Matija,

> This flag was recently removed [2] in nixpkgs with a comment:
> > The fix for gobject-introspection is in version 1.72.  

Maybe the fix didn't really fixed the problem ...

> Bottom line: If I compile Guile with patched libffi [3] dependency
> (where flag "disable-exec-static-tramp" is present) problematic
> examples are working (without patched G-Golf).

Perfect, just do that then, in nix guix as well (debian does, see below)

> Most probably has Debian present flag "disable-exec-static-tramp" when
> configuring libffi. Where can we check that?

Yes, in debian testing, libffi 3.4.6-1, the flag is on by default:

	https://codesearch.debian.net/search?q=disable-exec-static-tramp+pkg%3Alibffi

> I still wonder where is the problem, in Guile, G-Golf or
> gobject-introspection (which according to [2] should not be a
> problem).

Definitely not a g-golf bug. But since the flag has been introduced
precisely to deal with the yet to be fixed gobject-introspection, iiuc,
i would just continue to compile libffi passing the flag ...

Thanks,
David

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2024-09-02 21:18 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-21 14:50 G-Golf - Callback segmentation fault Matija Obid
2024-08-21 15:19 ` pelzflorian (Florian Pelz)
2024-08-23 23:57   ` David Pirotte
2024-08-24 16:01     ` pelzflorian (Florian Pelz)
2024-08-25  5:09       ` David Pirotte
2024-08-25 13:28         ` pelzflorian (Florian Pelz)
2024-08-26  6:40           ` pelzflorian (Florian Pelz)
2024-08-22  0:21 ` David Pirotte
2024-08-27 20:09   ` Matija Obid
2024-08-28 10:50     ` pelzflorian (Florian Pelz)
2024-08-29  0:18     ` David Pirotte
2024-08-31 16:35       ` Matija Obid
2024-09-02 15:30         ` pelzflorian (Florian Pelz)
2024-09-02 21:18         ` David Pirotte [this message]
2024-09-03  1:01           ` David Pirotte
2024-09-05  4:00             ` David Pirotte
2024-09-05  7:24               ` pelzflorian (Florian Pelz)
2024-09-05  7:42                 ` pelzflorian (Florian Pelz)
2024-09-05 21:23                   ` David Pirotte
2024-09-05 21:44                     ` David Pirotte
2024-09-05 20:48                 ` David Pirotte
2024-09-05 13:37               ` Matija Obid
2024-09-05 22:14                 ` David Pirotte
2024-09-06  6:29                   ` David Pirotte
2024-09-06  9:44                     ` pelzflorian (Florian Pelz)
2024-09-06 18:37                       ` David Pirotte
2024-09-06 22:08                         ` David Pirotte
2024-09-06 23:16                           ` David Pirotte
2024-09-07 14:08                             ` pelzflorian (Florian Pelz)
2024-09-07 11:53                           ` Matija Obid

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=20240902181854.2017f1fc@tintin \
    --to=david@altosw.be \
    --cc=guile-user@gnu.org \
    --cc=matija.obid@posteo.net \
    /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).