> On Thursday, February 27, 2025 at 02:48:43 AM PST, Michael Käppler > <xmichae...@web.de> 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 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? I don't cross-compile, which is why I always see so many more issues than others, haha. The build on Github spins up a Windows VM with a MinGW environment on it, and I build in that. > Also, what exactly is not functional in your build? Well, the very first problems I run into have nothing to do with the 64-bit problem, but, just basic bitrot. For some time, I had tried to ensure that the 32-bit, non-threaded, non-LTO, non-JIT version of Guile on MinGW kept working. But, it is broken on `main` again. The very first problems are - need win32 version of pagesize() - need to make sure that dlopen searches PATH on Win32 and handles DLLs of the form libfoo-X.dll in load-foreign-library I've got patches for these. > I have some more patches here that I contributed to fix Guile-Windows issues > in Lilypond. I can try to set up a repo on Github with all these patches > applied > on top of current Guile 'main'. > However, as we currently use Guile 3.0.10 to do releases, I would first have > to > make sure it still works with main. Don't worry about rebasing for now. I'd just like to see what you have working already in whatever form it is currently. My hope is that we can prefer your patches, and then I can tweak around them for any problems that remain. Regards, Mike Gran
