unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Jan Nieuwenhuizen <janneke@gnu.org>
To: guile-devel@gnu.org
Subject: Re: wip-mingw with x86_64 support updated for 3.0.8
Date: Mon, 16 May 2022 20:28:55 +0200	[thread overview]
Message-ID: <87zgjhxrfc.fsf@gnu.org> (raw)
In-Reply-To: <87r14zaglg.fsf@gnu.org> (Jan Nieuwenhuizen's message of "Wed, 11 May 2022 23:45:31 +0200")

Jan Nieuwenhuizen writes:

Hello again,

> I've reset and updated wip-mingw onto latest main:
>
>     https://git.savannah.gnu.org/cgit/guile.git/log/?h=wip-mingw

If you tried this with a recent Guix, you probably got a segfault.  I
finally found that compiling with -flto (--enable-lto) creates broken
DLLs with binutils > 2.35.2.  This is "fixed" by using --disable-lto
when compiling for mingw.

So, also with a recent Guix, this should work:

WINEPATH=$(guix shell wine64 -- winepath -w                                    \
   $(echo $(guix gc -R                                                         \
                 $(GUIX_PACKAGE_PATH=guix guix build                           \
                                    --target=x86_64-w64-mingw32 guile-mingw))) \
              | sed 's,$,/bin,g' | tr '\n' ';')                                \
       guix shell wine64 -- wine                                               \
       $(GUIX_PACKAGE_PATH=guix guix build --target=x86_64-w64-mingw32         \
                          guile-mingw)/bin/guile.exe                           \
       -c '(format #t "Hello ~a world!\n" %host-type)'

Greetings,
Janneke

-- 
Jan Nieuwenhuizen <janneke@gnu.org>  | GNU LilyPond https://lilypond.org
Freelance IT https://JoyOfSource.com | Avatar® https://AvatarAcademy.com



      reply	other threads:[~2022-05-16 18:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-11 21:45 wip-mingw with x86_64 support updated for 3.0.8 Jan Nieuwenhuizen
2022-05-16 18:28 ` Jan Nieuwenhuizen [this message]

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=87zgjhxrfc.fsf@gnu.org \
    --to=janneke@gnu.org \
    --cc=guile-devel@gnu.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).