Re: G-Golf - Callback segmentation fault

Hi again,

> > P.S. on Guix, I also no longer have to use --no-grafts, possibly
> > because Guix had major updates to core packages.  
> Excellent!

> > G-golf really satisfies now.  
> At last! Note that the above was not a g-golf problem [1].

Just want to make sure we are (all) on the same wave length here:
what really satisfies now is Guix, G-Golf always has.

David

> [1]

> And for that matter, nor is (a g-golf problem) the patch i just added
> to adapt to a GI/libffi api change that i was unaware of [2] - up to
> this upstream api change, g-golf has never failed to build and run an
> ffi-closure, ever since it implements callback and vfunc, all (the
> closure marshal machinery) entirely written in scheme by the way.

> [2]

> the gi doc tells us switch to call g-callable-info-create-closure when
> using gi >= 1.71.0, but fails to tells us that, starting with gi >=
> 1.72.0, the ffi-closure pointer we receive is no longer a 'native
> executable code pointer' ...

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEhCJlRZtBM3furJHe83T9k6MFetcFAmbaJkoACgkQ83T9k6MF
etcHigf/Ucky8IXOtJE4khzVxLlutrIvEK89fxjU/aoh5PFhSzughNoLY6y7nezs
B7LvT6DZtiMjWwcmIDt9JqHqJfpCaBL+gP0cI1cAlNi7RcxmSpltUrXsa138gPin
YokAUngrHbjzzzgiRnbctVZEFsl5/IQhmJDx1ibJ+FUVfi58AqM3PgY6V5whmyXi
NPzmjbE6R0afIPU1aUnEv85YC42gcl/6NAMf5oKqT6l0/QOoI6nc2WZWqn1gQ73w
eiNShEr/LY3veNqfh8VoUcanmEP6/nFNe7nwHfUHWK6UtQRQi1SkOwx27ZR/mjds
h4ib6eq9KO3FhERX1PipEC3jHL721w==
=ZtH6
-----END PGP SIGNATURE-----