<daviid>yes, grab an msys2 image, the latest of course, then launch/run it, in it (a terminal) run a few pacman commands to update it to the very latest, then use pacman to install guile, autoconf, automake, ssh ... what evert you need, then i cloned guile-cv and compiled install, then yes, just grab the window's dir (big, but ok ...) and send it ... <leoprikler>i think you mean "use pacman to install autoconf, automake, then install guile from source" ;) <leoprikler>come to think of it, could we do msys2 as a guix pack target? <daviid>leoprikler: at the time, guile-3.0 didn't even exist, and guile-cv runs fine with 2.2 ... but i think if one email the msys2 guile packages mainainter, they might easily get guile-3.0 (not me, at least not 'now' ... but my intuition is that it should be easy forthe maintainer ...) <morganw>From what I had read it last I don't think it would build, and there was a suggestion that it might be possible to get it working again without threading support and 32-bit only. <daviid>morganw: don't confusewindow 'native' guile compilationand msys2, mingw-64, that hasnothing todowith one another... <morganw>aren't msys2 ports built with mingw ? <daviid>morganw: look/read the msys2 homepage, thewiki ... it has everything you need toknow <leoprikler>yeah, but the way packages are partitioned is a bit weird <leoprikler>I was looking in the github repo if that helps understanding :) <daviid>it even has gtk4 4.2.0 (debian only has 4.0.3) :) <daviid>and GI, so g-golf will also run on msys2 ... <daviid>the msys2 folks are extremely nice as well, i had (back then) to ask for help, #msys2 on oftc fwiw ... <dsmith>A special thanks to those brave souls who labor tirelessly to bring free software to those under the oppression and tryanny of M$ <sarna>"Guile only adopted with-exception-handler and raise-exception as its primary exception-handling facility in 2019." - how much of real-life code uses exceptions instead of the legacy stuff? ***rt is now known as robin
***apteryx_ is now known as apteryx
<apteryx>FTR I wasn't able to test guile on Android because my Android is not root, and the Guix relocation option for aarch64-linux is not currently usable due to proot-static failing to build on that platform <civodul>apteryx: hi! maybe you can skip proot tests to see how it goes? ***xws is now known as wxie
<apteryx>hm, it fails during the build phase, not the check phase ***Guest7431 is now known as chrislck
<sarna>btw, guile runs fine on iOS with iSH :^) <sarna>it's emulating i686 linux, so it's not the fastest - but it works <civodul>apteryx: you could also hack around to remove the proot "engine", so that you can at least try the "fakechroot" engine <apteryx>sarna: good to know! We should compile a list of these hacks somewhere, so that someone can have an overview of the Guile cross-platform picture. <apteryx>I'll try building that previous version <civodul>apteryx: another option would be to allow -RR without the "proot" engine <apteryx>v4.0.3 could be built for aarch64-linux <apteryx>I'll open an issue on the project's tracker <apteryx>for the record I used: guix build proot --with-git-url=proot=https://github.com/proot-me/proot --with-commit=proot=v4.0.3 --without-tests=proot --system=aarch64-linux to validate this (I had to make a minor change to the package def so its test suite would be skipped) <apteryx>transformation options are really handy! <iwan>how can I run subset of guile tests? e.g. elisp.test <civodul>iwan: you can run: ./check-guile elisp.test ***xws is now known as wxie