From: "Thompson, David" <dthompson2@worcester.edu>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-devel <guile-devel@gnu.org>,
"Rob Browning" <rlb@defaultvalue.org>,
"Aleix Conchillo Flaqué <aconchillo@gmail.com>,
Greg Troxel <gdt@lexort.com>,
Sergei Trofimovich" <slyfox@gentoo.org>
Subject: Re: GNU Guile 3.0.9rc1 available for testing!
Date: Fri, 20 Jan 2023 11:18:10 -0500 [thread overview]
Message-ID: <CAJ=RwfYUSk86OUO2n3XAO6nDUYLnUHXyuG24bmi0wE_jOmwQ-Q@mail.gmail.com> (raw)
In-Reply-To: <87v8l15hb2.fsf@inria.fr>
Hi Ludo,
On Fri, Jan 20, 2023 at 10:58 AM Ludovic Courtès <ludo@gnu.org> wrote:
>
> Please report any issues you may find. I’m particularly interested in
> portability regressions (NetBSD and other BSDs, macOS, MinGW, as well as
> architectures other than x86_64).
I was curious about the MinGW build, so I used a Guix command you
shared to build it:
guix build guile-next --with-git-url=guile-next=$HOME/Code/guile
--with-branch=guile-next=main --target=x86_64-w64-mingw32
I then copied the resulting /gnu/store directory somewhere writable,
copied over all the DLLs (libgc, libunistring, etc.) it needed from
/gnu/store into the 'bin' directory, and tried running with wine64 but
it failed:
```
$ guix shell wine64 -- wine64 guile.exe
MESA-INTEL: warning: Performance support disabled, consider sysctl
dev.i915.perf_stream_paranoid=0
0084:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0084:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0084:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0084:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
Mingw-w64 runtime failure:
32 bit pseudo relocation at 0000000140001568 out of range, targeting
0000000319370E80, yielding the value 00000001D936F914.
abnormal program termination
```
Maybe someone else would like to give it a shot? Or even try running
it on Windows? I hadn't tried in years, but my last experience with a
Guile MinGW build required either disabling threads and JIT or trying
to apply various patches people had floating around. So, to see a
build complete with just the upstream source and without disabling
anything is very promising!
Thanks for all the hard work on the release!
- Dave
next prev parent reply other threads:[~2023-01-20 16:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 15:58 GNU Guile 3.0.9rc1 available for testing! Ludovic Courtès
2023-01-20 16:18 ` Thompson, David [this message]
2023-01-21 14:58 ` Jan Nieuwenhuizen
2023-01-23 10:42 ` Ludovic Courtès
2023-01-23 13:23 ` Janneke Nieuwenhuizen
2023-01-20 17:50 ` Aleix Conchillo Flaqué
2023-01-23 10:45 ` Ludovic Courtès
2023-01-23 17:01 ` Aleix Conchillo Flaqué
2023-01-22 2:12 ` Greg Troxel
2023-01-22 14:30 ` lloda
2023-01-22 14:39 ` Greg Troxel
2023-01-23 10:48 ` Ludovic Courtès
2023-01-23 18:04 ` lloda
2023-01-23 21:59 ` bug#60971: build failure of v3.0.9rc1 on mac os 12.6 Ludovic Courtès
2023-01-23 18:47 ` GNU Guile 3.0.9rc1 available for testing! Aleix Conchillo Flaqué
2023-01-25 1:44 ` Greg Troxel
2023-01-25 10:32 ` Ludovic Courtès
2023-01-22 17:41 ` Greg Troxel
2023-01-22 23:10 ` Greg Troxel
2023-01-23 11:02 ` Ludovic Courtès
2023-01-23 11:19 ` Ludovic Courtès
2023-01-24 15:43 ` Greg Troxel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ=RwfYUSk86OUO2n3XAO6nDUYLnUHXyuG24bmi0wE_jOmwQ-Q@mail.gmail.com' \
--to=dthompson2@worcester.edu \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=rlb@defaultvalue.org \
--cc=slyfox@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).