Re: Welcoming Olivier as new committer
Jonas Hahnfeld via "Developers list for Guile, the GNU extensibility library" <[email protected]> Tue, 03 Mar 2026 19:56:58 +0100
| Newsgroups | gmane.lisp.guile.devel |
|---|---|
| Message-ID | <[email protected]> |
--=-+a0CVpW1n8i8JH8ZkAcA Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, 2026-03-03 at 19:35 +0100, Janneke Nieuwenhuizen wrote: > Janneke Nieuwenhuizen writes: > > Jonas Hahnfeld writes: > > > > and never got merged. So we've just been patching Guile ourselves = (to > > > > create Windows binaries for Dezyne, for example). Recently, Jonas > > > > Hahnfeld managed to split that patch up in several bits, make fixes= for > > > > lightening, and get it merged; lovely! > > >=20 > > > I would like to clarify that I *did not* split up the patch because i= t > > > was entirely based on the concept of requiring and patching mini-gmp. > > > The merged changes work with upstream interfaces of GMP, at the expen= se > > > of a slightly slower conversion in case the value at run-time falls > > > between 2**32 and 2**64 and does not fit into long. > >=20 > > Ah sorry, I totally missed that. But your patch still adheres to the > > requirement of having identical .go files for any 64-bit system, right? >=20 > Hmm, I'm really puzzled now. In=20 >=20 > https://codeberg.org/guile/guile/pulls/90#issuecomment-9744014 >=20 > I believe it's you (? I'm not all that great with these newfangled GUI > interfaces) who replies to my >=20 > >> I'll be looking at that next for =3Dwip-mingw-2026=3D, which inter= estingly, > >> "lacks" the huge x86_64-mingw32 commit that we've been working wit= h for > >> years. >=20 > with >=20 > > AFAICT the commit has been split up, [..] >=20 > What am I missing? Yeah, rereading it now my comment is not quite understandable. What I'm trying to say is that the branch doesn't *lack* the huge x86_64-mingw32 commit but it's there is some smaller pieces and explaining how #22 is following a different approach. --=-+a0CVpW1n8i8JH8ZkAcA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQRiF4DLRvon1vw5biCcVOmY/6OEDwUCaacu+wAKCRCcVOmY/6OE D7D1AP9ShXyEegGETjjynOuvq1d8kujaLVu+ixdcWd43IG4K4QEA2bDaLOGRxVu5 S60WisIhTk+1UVLf1twaQrl8q/OadQg= =nuFk -----END PGP SIGNATURE----- --=-+a0CVpW1n8i8JH8ZkAcA--