unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Christoph Buck <christoph.buck@smartoptics.de>
To: <guile-devel@gnu.org>
Subject: Compiling guile-2.2.4 for mingw
Date: Tue, 20 Nov 2018 15:31:25 +0100	[thread overview]
Message-ID: <xxt7eh7lt1e.fsf@smartoptics.de> (raw)

Hi!

Currently i try to compile guile-2.2.4 under mingw64 bit. I had some
minor issues in the c source code which i managed to fix by applying
some of the patches from https://github.com/mkeeter/guile-mingw. Namely 

1) 0003-winsock-compat.mingw.patch
2) 0004-start_child.mingw.patch

Now i am at the point where i have a working guile binary and the helper
scripts in the meta directory. But at this point the boostrapping fails
with the following error:

> make[2]: Entering directory '/home/Christoph.Buck/guile-2.2.4/bootstrap'
>   BOOTSTRAP GUILEC ice-9/eval.go
> Backtrace:
> In ice-9/eval.scm:
>     619:8 19 (_ #(#(#<directory (guile-user) 42c5f00>)))
>     155:9 18 (_ _)
> In srfi/srfi-1.scm:
>     640:9 17 (for-each #<procedure 4f5df20 at ice-9/eval.scm:333:13▒> ▒)
> In ice-9/eval.scm:
>     163:9 16 (_ _)
> In ice-9/boot-9.scm:
>     152:2 15 (with-fluid* _ _ _)
> In system/base/target.scm:
>      57:6 14 (with-target _ _)
> In system/base/compile.scm:
>     152:6 13 (compile-file _ #:output-file _ #:from _ #:to _ #:env _ ▒)
>      43:4 12 (call-once _)
> In ice-9/boot-9.scm:
>     841:4 11 (with-throw-handler _ _ _)
> In system/base/compile.scm:
>     59:11 10 (_)
>    155:11  9 (_ #<closed: file 42abaf0>)
>    224:14  8 (read-and-compile _ #:from _ #:to _ #:env _ #:opts _)
>     255:6  7 (compile _ #:from _ #:to _ #:env _ #:opts _)
>    183:32  6 (compile-fold _ _ _ (#:to-file? #t #:warnings (#) # #t ▒))
> In language/cps/compile-bytecode.scm:
>    591:12  5 (emit-bytecode _ #<module (#{ g135}#) 4d77dc0> _)
> In ice-9/eval.scm:
>     163:9  4 (_ #(#(#<directory (system vm assembler) 4f773c0>) # #t))
> In unknown file:
>            3 (_ #<procedure 6675b80 at ice-9/eval.scm:330:13 ()> #<▒> ▒)
> In ice-9/eval.scm:
>     619:8  2 (_ #(#(#(#(#(#(#(#(#(#(#(▒) ▒) ▒) ▒) ▒) ▒) ▒) ▒) ▒) ▒) ▒))
> In unknown file:
>            1 (bytevector-u64-set! #vu8(0 0 0 0 0 0 0 0 0 0 0 0 0 0 ▒) ▒)
> In ice-9/boot-9.scm:
>    752:25  0 (dispatch-exception _ _ _)

> ice-9/boot-9.scm:752:25: In procedure dispatch-exception:
> In procedure bytevector-u64-set!: Value out of range: -149659645
> make[2]: *** [Makefile:1931: ice-9/eval.go] Error 1
> make[2]: Leaving directory '/home/Christoph.Buck/guile-2.2.4/bootstrap'
> make[1]: *** [Makefile:1857: all-recursive] Error 1
> make[1]: Leaving directory '/home/Christoph.Buck/guile-2.2.4'
> make: *** [Makefile:1743: all] Error 2

I have no idea what might be wrong here or how to fix this problem. Does
anbody have an idea?

Best regards

Christoph Buck



             reply	other threads:[~2018-11-20 14:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-20 14:31 Christoph Buck [this message]
2018-11-20 15:39 ` Compiling guile-2.2.4 for mingw tomas
2018-11-20 15:59 ` Mike Gran
2018-11-20 17:16   ` Christoph Buck
2018-11-20 17:45     ` Mike Gran
2018-11-20 20:27       ` Mark H Weaver
2018-11-20 17:10 ` Eli Zaretskii
2018-11-20 17:53 ` 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=xxt7eh7lt1e.fsf@smartoptics.de \
    --to=christoph.buck@smartoptics.de \
    --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).