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

Hi!

I've reset and updated wip-mingw onto latest main:

    https://git.savannah.gnu.org/cgit/guile.git/log/?h=wip-mingw

Most changes are simply a continuation of the previous
x86_64-w64-mingw32 work done for 3.0.7, using intptr_t and uintptr_t
instead of scm_t_inum or long and unsigned long.

There's one new problem though, the fix I made to determine
file-name-convention correctly when (cross)compiling and when running
now does not work anymore.

FIXME in 3.0.7, this works:

  ;; boot-9.scm
  (define (compile-time-file-name-convention)
    (let ((target ((@ (system base target) target-type))))
      (cond ((equal? target %host-type)
             (system-file-name-convention))
            ((string-contains-ci target "mingw")
             'windows)
            (else
             'posix)))))

in 3.0.8 it aborts hard.

    guile: uncaught exception:
    Unbound variable:define-module
    Cannot exit gracefully when init is in progress; aborting.

Anyway, I gave up and changed it back to 'posix always using this hack:

    (let ((target (or "FIXME" ((@ (system base target) target-type)))))

with a MinGW-specific for cross-compiling to MinGW to 'windows always:

    (let ((target (or "mingw" "FIXME" ((@ (system base target) target-type)))))

Ugh.  Ideas for a proper fix much appreciated!

Other than that, guile-mingw can still be built by doing

    GUIX_PACKAGE_PATH=guix guix build guile-mingw

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-11 21:45 UTC|newest]

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

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=87r14zaglg.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).