Mike Gran writes:
> So I'm still plugging away at this Guile on Windows stuff.
Thank you for keeping us up to date!
> Guile's use of BDW GC is complicated. It is not the
> "just replace malloc with GC_MALLOC" described
> in the BDW GC docs.
Are you aware of the work done on whippet to replace
"Dr. Arne Babenhauserheide" writes:
> Mike Gran writes:
>> bootstrapped with the bitrotten guts of what we had before to get back
>> to a working `make check`. From here, it might be simple to extract
>> the old 64-bit patch and incorporate the Lilypond patch set in whole or
>> in part. I don'
Mike Gran writes:
> bootstrapped with the bitrotten guts of what we had before to get back
> to a working `make check`. From here, it might be simple to extract
> the old 64-bit patch and incorporate the Lilypond patch set in whole or
> in part. I don't know yet. I haven't tried it.
…
> - rlb ex
Jonas Hahnfeld writes:
> On Thu, 2025-03-20 at 09:21 -0700, Mike Gran wrote:
>> "Dr. Arne Babenhauserheide" writes:
>> > Did you manage to move forward with the patches?
>>
>> That CI/CD is running my old Guile patchset. So now I'm actually ready
>> to replace my Guile patchset with mainline G
Jonas Hahnfeld writes:
> On Sun, 2025-03-30 at 23:08 -0700, Mike Gran wrote:
>> Mike Gran writes:
>>
>> I've created a new branch in the main Guile repo on savannah called
>> wip-guile-2025, pulling in enough of various patchsets to get `make` and
>> `make check` to run on 64-bit, threaded, JIT
On Mon, 2025-03-31 at 12:15 +0200, Dr. Arne Babenhauserheide wrote:
> @Jean: Are there additional changes needed in the branch—besides the
>polishing Mike is doing—so Lilypond can fully switch to Guile 3?
LilyPond is already using Guile 3 since more than a year now (January
2024). Also on
On Sun, 2025-03-30 at 23:08 -0700, Mike Gran wrote:
> Mike Gran writes:
>
> > I'm making progress. I just pushed back into Guile's main branch a
> > patchset that makes the 32-bit MinGW build again, which was broken. The
> > 32-bit build is now working on my native MinGW on Windows 11, and I'll
Mike Gran writes:
> Mike Gran writes:
> I've created a new branch in the main Guile repo on savannah called
> wip-guile-2025, pulling in enough of various patchsets to get `make` and
…
> There are no actions required by anyone at this point, but, I'll need
> some review once I have a tree I'm ha
Mike Gran writes:
> I'm making progress. I just pushed back into Guile's main branch a
> patchset that makes the 32-bit MinGW build again, which was broken. The
> 32-bit build is now working on my native MinGW on Windows 11, and I'll
> know today if it works on Guix's CI cross-build.
>
> Assumin
"Dr. Arne Babenhauserheide" writes:
> Hi Jonas, Hi Mike,
>
> Jonas Hahnfeld via "Developers list for Guile, the GNU extensibility
> library" writes:
>
>> The full set of patches can be found here:
>> https://gitlab.com/lilypond/lilypond/-/tree/master/release/binaries/patches
>> and the build con
Mike Gran writes:
>> Did you manage to move forward with the patches?
> Things are in progress, but since I've been out of the free software
> scene for a while, it took me a bit to pull things together: linux box
> figure out emacs mail again, IMAP, SMTP, debbugs, git am, etc. Patches
> are tough
On Thu, 2025-03-20 at 09:21 -0700, Mike Gran wrote:
> "Dr. Arne Babenhauserheide" writes:
> > Did you manage to move forward with the patches?
>
> That CI/CD is running my old Guile patchset. So now I'm actually ready
> to replace my Guile patchset with mainline Guile and then the Lilypond
> pat
Hi Jonas, Hi Mike,
Jonas Hahnfeld via "Developers list for Guile, the GNU extensibility library"
writes:
>> If someone wants to point me to a complete source tarball
>> to diff with main or some other additional source of information,
>> I can continue my evaluation. Else, I can use these pa
On Tue, 2025-02-25 at 23:07 +, Mike Gran wrote:
> First off, these patches look good to me. They are necessary if we want to
> try to support Windows. Plus Jonas figured out a couple of the errors I never
> managed
> to work out with Lightning and the VM. So I'm very impressed.
>
> A couple o
On Thu, 2025-02-27 at 04:12 +, Mike Gran wrote:
> OK. This patchset does not result in a functional build on any of the Win32
> VMs I've tested. It seems necessary but not sufficient. I feel like there
> needs to be a few more patches that should have been attached. I could fairly
> easily t
Am 27.02.2025 um 17:55 schrieb Mike Gran:
Can you share details about your compilation and testing setup?
I applied the patches to main and added some VMs at
github.com/spk121/guile-jonas
Thanks, very helpful.
Also, what exactly is not functional in your build?
Well, the very first problems
> Date: Thu, 27 Feb 2025 16:55:54 + (UTC)
> From: Mike Gran
> Cc: "hah...@hahnjo.de"
>
> - need to make sure that dlopen searches PATH on Win32
This is guaranteed by the algorithm used by Windows APIs that load
DLLs (which dlopen calls) -- assuming that dlopen you use is the one
that comes
> On Thursday, February 27, 2025 at 02:48:43 AM PST, Michael Käppler
> wrote:
> Sorry, somehow the rest of my message got truncated...
> Can you share details about your compilation and testing setup?
I applied the patches to main and added some VMs at
github.com/spk121/guile-jonas
> In part
Sorry, somehow the rest of my message got truncated...
Can you share details about your compilation and testing setup?
In particular, the mingw toolchain (GCC-UCRT?) and the VMs used for testing. As
you write about VMs, I assume you cross-compiled from a Linux environment?
Also, what exactly is n
Hi Mike,
thanks a lot for testing!
I'm excited to see this finally going forward.
>OK. This patchset does not result in a functional build on any of the Win32
>VMs I've tested. It seems necessary but not sufficient.
Can you share details about your compilation and testing setup?
In particul
OK. This patchset does not result in a functional build on any of the Win32
VMs I've tested. It seems necessary but not sufficient. I feel like there
needs to be a few more patches that should have been attached. I could fairly
easily
tweak it into shape, but, I'd rather make sure I've got the
>> If we do care about building with the native MinGW toolchain,
>> in my humble opinion, there isn't much value in supporting then many
>> versions of MinGW other than UCRT64.
> Is there any doco on how to do that?
Well these days, as far as I can tell, the MinGW that lives on Sourceforge
seems
> On 26 Feb 2025, at 9:37 am, Mike wrote:
> Jonas et al-
>
> OK. Probably against my better judgement, haha, I'm going to try to help.
>
> First off, these patches look good to me. They are necessary if we want to
> try to support Windows. Plus Jonas figured out a couple of the errors I never
Jonas et al-
OK. Probably against my better judgement, haha, I'm going to try to help.
First off, these patches look good to me. They are necessary if we want to
try to support Windows. Plus Jonas figured out a couple of the errors I never
managed
to work out with Lightning and the VM. So I'm ve
> On Monday, February 24, 2025 at 03:03:13 PM PST, Dr. Arne Babenhauserheide
> wrote:
> Jonas Hahnfeld writes:
>> If I'm honest, it would help more to get reviews from people actually
>> looking at the code...
> For some context: we are struggling to find people with experience in
> Windows an
Jonas Hahnfeld via "Developers list for Guile, the GNU extensibility
library" writes:
> This should be the case, I always make sure that all intermediate
> states compile. If I missed something, please let me know where you
> see a failure.
Sorry, that was just a mireading on my part.
> Shorter
Jonas Hahnfeld writes:
> If I'm honest, it would help more to get reviews from people actually
> looking at the code...
For some context: we are struggling to find people with experience in
Windows and rlb went as deep as was possible in their limited time.
I asked rlb to provide the feedback th
On Thu, 2025-02-20 at 12:18 -0600, Rob Browning wrote:
> "Dr. Arne Babenhauserheide" writes:
>
> > I tried to ping in IRC again, but since no one seems fit to do the
> > reviews, I put it on my own TODO list.
>
> So this belongs in the category of somewhat cursory comments, and I'm
> not sure I
On Thu, 2025-02-20 at 18:56 +, Chris Vine wrote:
> On Thu, 20 Feb 2025 12:18:19 -0600
> Rob Browning wrote:
> > - I also wondered if there are any existing platforms where
> > sizeof(intptr_t) != sizeof(long)
>
> I have not been following your exchanges, but on 64-bit Windows longs
> ar
On Thu, 20 Feb 2025 12:18:19 -0600
Rob Browning wrote:
> - I also wondered if there are any existing platforms where
> sizeof(intptr_t) != sizeof(long)
I have not been following your exchanges, but on 64-bit Windows longs
are the same size as int, namely 32 bits. 'long long' and pointers ar
"Dr. Arne Babenhauserheide" writes:
> I tried to ping in IRC again, but since no one seems fit to do the
> reviews, I put it on my own TODO list.
So this belongs in the category of somewhat cursory comments, and I'm
not sure I should be the more substantive reviewer here, and/or have
the time to
Hi Jonas,
Thank you for the rebased patches!
Jonas Hahnfeld via "Developers list for Guile, the GNU extensibility library"
writes:
> Another ping on this thread. Just to remind, this is important for
> LilyPond, which is a fellow GNU project.
>
> I'm attaching the first five patches required to
On Sun, 2024-07-14 at 20:30 +0200, Jonas Hahnfeld wrote:
> On Wed, 2024-03-20 at 21:28 +0100, Jonas Hahnfeld wrote:
> > I'm also explicitly CC'ing Andy and Ludo - we really need a statement
> > by a maintainer whether this can land. From my point of view, it's a
> > clear improvement in terms of su
Jonas Hahnfeld via "Developers list for Guile, the GNU extensibility library"
writes:
> On Wed, 2024-03-20 at 21:28 +0100, Jonas Hahnfeld wrote:
>> I'm also explicitly CC'ing Andy and Ludo - we really need a statement
>> by a maintainer whether this can land. From my point of view, it's a
>> cle
On Wed, 2024-03-20 at 21:28 +0100, Jonas Hahnfeld wrote:
> I'm also explicitly CC'ing Andy and Ludo - we really need a statement
> by a maintainer whether this can land. From my point of view, it's a
> clear improvement in terms of supported platforms, plus tested by
> LilyPond since some time now
On Sat, Mar 23, 2024 at 11:09 AM Jonas Hahnfeld wrote:
>
> On Wed, 2024-03-20 at 16:40 -0400, Thompson, David wrote:
> > On Wed, Mar 20, 2024 at 4:29 PM Jonas Hahnfeld wrote:
> > > So I can confirm that JIT indeed doesn't work right now on 64-bit
> > > MinGW, but it's relatively easy to fix (firs
On Wed, 2024-03-20 at 16:40 -0400, Thompson, David wrote:
> On Wed, Mar 20, 2024 at 4:29 PM Jonas Hahnfeld wrote:
> > So I can confirm that JIT indeed doesn't work right now on 64-bit
> > MinGW, but it's relatively easy to fix (first patch). In essence
> > lightening was getting the calling conven
On Wed, Mar 20, 2024 at 4:29 PM Jonas Hahnfeld wrote:
>
> So I can confirm that JIT indeed doesn't work right now on 64-bit
> MinGW, but it's relatively easy to fix (first patch). In essence
> lightening was getting the calling convention wrong.
Wow! Have you seen the JIT do its thing (via GUILE_
On Wed, 2024-02-07 at 21:29 +0100, Jonas Hahnfeld via Developers list
for Guile, the GNU extensibility library wrote:
> On Wed, 2024-02-07 at 15:23 -0500, Thompson, David wrote:
> > On Wed, Feb 7, 2024 at 3:19 PM Jonas Hahnfeld wrote:
> > >
> > > On Wed, 2024-02-07 at 09:19 -0500, Thompson, David
On Wed, 2024-02-07 at 15:23 -0500, Thompson, David wrote:
> On Wed, Feb 7, 2024 at 3:19 PM Jonas Hahnfeld wrote:
> >
> > On Wed, 2024-02-07 at 09:19 -0500, Thompson, David wrote:
> > > On Thu, Jan 4, 2024 at 5:40 AM Jonas Hahnfeld via Developers list for
> > > Guile, the GNU extensibility library
On Wed, Feb 7, 2024 at 3:19 PM Jonas Hahnfeld wrote:
>
> On Wed, 2024-02-07 at 09:19 -0500, Thompson, David wrote:
> > On Thu, Jan 4, 2024 at 5:40 AM Jonas Hahnfeld via Developers list for
> > Guile, the GNU extensibility library wrote:
> > >
> > > On Tue, 2023-11-28 at 22:04 +0100, Jonas Hahnfel
On Wed, 2024-02-07 at 09:19 -0500, Thompson, David wrote:
> On Thu, Jan 4, 2024 at 5:40 AM Jonas Hahnfeld via Developers list for
> Guile, the GNU extensibility library wrote:
> >
> > On Tue, 2023-11-28 at 22:04 +0100, Jonas Hahnfeld wrote:
> > >
> > > Ping, any comments on this approach? I buil
On Thu, Jan 4, 2024 at 5:40 AM Jonas Hahnfeld via Developers list for
Guile, the GNU extensibility library wrote:
>
> On Tue, 2023-11-28 at 22:04 +0100, Jonas Hahnfeld wrote:
> >
> > Ping, any comments on this approach? I built binaries for LilyPond
> > 2.25.10 using these patches applied on top o
Jonas Hahnfeld via "Developers list for Guile, the GNU extensibility library"
writes:
> On Tue, 2023-11-28 at 22:04 +0100, Jonas Hahnfeld wrote:
>> On Sun, 2023-10-29 at 22:34 +0100, Jonas Hahnfeld wrote:
>> > I would like to propose a different approach: It turns out to be
>> > possible to just
On Tue, 2023-11-28 at 22:04 +0100, Jonas Hahnfeld wrote:
> On Sun, 2023-10-29 at 22:34 +0100, Jonas Hahnfeld wrote:
> > On Tue, 2023-06-06 at 20:50 +, Mike Gran wrote:
> > > Hello Guile,
> >
> > Hi Mike,
> >
> > I'm sorry for "necrobumping" this thread; I wanted to reply back in
> > June but
Jonas Hahnfeld via "Developers list for Guile, the GNU extensibility library"
writes:
>> What do you and others think of this approach, would this be "more"
>> acceptable to land in main?
>
> Ping, any comments on this approach? I built binaries for LilyPond
> 2.25.10 using these patches applied
On Sun, 2023-10-29 at 22:34 +0100, Jonas Hahnfeld wrote:
> On Tue, 2023-06-06 at 20:50 +, Mike Gran wrote:
> > Hello Guile,
>
> Hi Mike,
>
> I'm sorry for "necrobumping" this thread; I wanted to reply back in
> June but didn't have enough time to work through what I will explain
> further bel
On Tue, 2023-06-06 at 20:50 +, Mike Gran wrote:
> Hello Guile,
Hi Mike,
I'm sorry for "necrobumping" this thread; I wanted to reply back in
June but didn't have enough time to work through what I will explain
further below. In any case, I would very much like to see good Windows
64-bit suppor
Hey Guile-
So I'm still plugging away at this Guile on Windows stuff.
In a tree on Github [1], I started from the top and cleaned up
the 64-bit Cygwin and MSYS problems. Cygwin and MSYS
are two related projects where you compile with GCC,
with the newlib C library, and a link to a library that
p
Op 08-06-2023 om 22:46 schreef Mike Gran:
But when I get back to it, I'll try to be more precise
1. long or long long - an integer that is "big" in some general sense
2. int64_t - an integer that needs to be 64-bit because may hold a large integer
3. intptr_t - an integer that holds a pointer
> (The following response is a bit muddled -- it initially says I don't
> follow but later I will. Still, there is some stuff of which I really
> disagree with the implementation.)
> I don't quite follow why the change from 'long' to 'intptr_t'. I mean,
> reading the commit message you linked t
Op 06-06-2023 om 22:50 schreef Mike Gran:
Hello Guile,
There have been a few times where I made Guile work on
MinGW -- usually the 32-bit, unthreaded variety -- because I wanted it
for my own entertainment. Often around the time of the Lisp Game Jam.
The Game Jam just happened, so I was pokin
On Tuesday, June 6, 2023 at 02:10:25 PM PDT, Thompson, David
wrote:
...
>> Janneke has also poked at Windows support a few times as well, and
>> he actually got it to run on 64-bit Windows.
>Did JIT work? When I tried this years ago it didn't. Would be a major
>victory if it works now.
There
Hi Mike,
On Tue, Jun 6, 2023 at 4:51 PM Mike Gran wrote:
>
> Hello Guile,
>
> There have been a few times where I made Guile work on
> MinGW -- usually the 32-bit, unthreaded variety -- because I wanted it
> for my own entertainment. Often around the time of the Lisp Game Jam.
> The Game Jam jus
Le mardi 06 juin 2023 à 20:50 +, Mike Gran a écrit :
> Also, it might be that this isn't worth doing. After all, you can run
> Guile on Cygwin and Guix on WSL on Windows 10/11 already.
> But some projects that depend on Guile do deliver on
> Windows using customized versions of 2.2 or 1.8.
Hello Guile,
There have been a few times where I made Guile work on
MinGW -- usually the 32-bit, unthreaded variety -- because I wanted it
for my own entertainment. Often around the time of the Lisp Game Jam.
The Game Jam just happened, so I was poking it again. Although
I never actually delive
56 matches
Mail list logo
