* bug#14171: REPL doesn't work on windows min-gw
@ 2013-04-10 3:59 Jan Schukat
2013-04-10 20:23 ` Andy Wingo
0 siblings, 1 reply; 6+ messages in thread
From: Jan Schukat @ 2013-04-10 3:59 UTC (permalink / raw)
To: 14171
[-- Attachment #1: Type: text/html, Size: 2738 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#14171: REPL doesn't work on windows min-gw
2013-04-10 3:59 bug#14171: REPL doesn't work on windows min-gw Jan Schukat
@ 2013-04-10 20:23 ` Andy Wingo
2013-04-11 14:40 ` bug#14171: Aw: " Jan Schukat
0 siblings, 1 reply; 6+ messages in thread
From: Andy Wingo @ 2013-04-10 20:23 UTC (permalink / raw)
To: Jan Schukat; +Cc: 14171
On Wed 10 Apr 2013 05:59, "Jan Schukat" <shookie@email.de> writes:
> system/repl/common.scm:147:25: In procedure make-repl:
> system/repl/common.scm:147:25: In procedure module-lookup: Unbound
> variable: times
Can you try with the 2.0.9 release, made yesterday? It should fix this
error.
Andy
--
http://wingolog.org/
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#14171: Aw: Re: bug#14171: REPL doesn't work on windows min-gw
2013-04-10 20:23 ` Andy Wingo
@ 2013-04-11 14:40 ` Jan Schukat
2013-04-14 17:26 ` Mark H Weaver
2013-04-15 6:37 ` Jan Schukat
0 siblings, 2 replies; 6+ messages in thread
From: Jan Schukat @ 2013-04-11 14:40 UTC (permalink / raw)
To: Andy Wingo; +Cc: 14171
[-- Attachment #1: Type: text/html, Size: 1691 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#14171: Aw: Re: bug#14171: REPL doesn't work on windows min-gw
2013-04-11 14:40 ` bug#14171: Aw: " Jan Schukat
@ 2013-04-14 17:26 ` Mark H Weaver
2013-04-15 6:37 ` Jan Schukat
1 sibling, 0 replies; 6+ messages in thread
From: Mark H Weaver @ 2013-04-14 17:26 UTC (permalink / raw)
To: Jan Schukat; +Cc: 14171
[-- Attachment #1: Type: text/plain, Size: 955 bytes --]
"Jan Schukat" <shookie@email.de> writes:
> Ok, did use this package: guile-2.0.9.2-f480a-dirty.tar.gz and can
> build and run guile-2.0 on mingw when I --disable-posix, which makes
> sense, since Windows is not posix :) Can even use threads.
> I guess I try to get the test-suite to run now.
> I'm pretty happy now that my issues on windows could be resolved in
> the last few weeks.
Excellent! :)
FYI, LRN on #gnunet reported the same issue (Guile REPL hangs on mingw),
and --disable-posix fixed the problem for him as well. He provided a
backtrace (generated by ProcessHacker; gdb didn't generate a useful
backtrace), and I've attached it below.
He also reported that, when built with --enable-posix, control reached
the start of 'top-repl', but never reached 'start-repl'. The backtrace
seems to suggest that the lockup might be happening within 'sigaction',
which is called from 'call-with-sigint' in (ice-9 top-repl).
Regards,
Mark
[-- Attachment #2: Backtrace of Guile REPL hang on mingw32 with --enable-posix --]
[-- Type: text/plain, Size: 3348 bytes --]
0, ntoskrnl.exe!_misaligned_access+0x17e7
1, ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x93d
2, ntoskrnl.exe!KeWaitForSingleObject+0x19f
3, ntoskrnl.exe!_misaligned_access+0xba4
4, ntoskrnl.exe!_misaligned_access+0x1821
5, ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x93d
6, ntoskrnl.exe!KeWaitForMultipleObjects+0x26a
7, ntoskrnl.exe!NtWaitForSingleObject+0x40f
8, ntoskrnl.exe!IoReportTargetDeviceChange+0xe6d
9, ntoskrnl.exe!KeSynchronizeExecution+0x3a23
10, wow64cpu.dll!TurboDispatchJumpAddressEnd+0x6c0
11, wow64cpu.dll!TurboDispatchJumpAddressEnd+0xf5
12, wow64.dll!Wow64SystemServiceEx+0x1ce
13, wow64.dll!Wow64LdrpInitialize+0x429
14, ntdll.dll!RtlUniform+0x6e6
15, ntdll.dll!RtlCreateTagHeap+0xa7
16, ntdll.dll!LdrInitializeThunk+0xe
17, ntdll.dll!ZwWaitForMultipleObjects+0x15
18, kernel32.dll!WaitForMultipleObjectsEx+0x8e
19, kernel32.dll!WaitForMultipleObjects+0x18
20, libwinpthread-1.dll!pthread_cond_init+0x1f8
21, libwinpthread-1.dll!pthread_tls_init+0x503
22, libwinpthread-1.dll!pthread_cond_init+0x510
23, libwinpthread-1.dll!pthread_cond_wait+0x138
24, libgcc_s_sjlj-1.dll!_emutls_get_address+0x52
25, libguile-2.0-22.dll!scm_spawn_thread+0xc6
26, libguile-2.0-22.dll!scm_init_rw+0x8c
27, libwinpthread-1.dll!pthread_once+0xae
28, libguile-2.0-22.dll!scm_sigaction_for_thread+0x7f
29, libguile-2.0-22.dll!scm_primitive_eval+0x34
30, libguile-2.0-22.dll!scm_call_4+0x48
31, libguile-2.0-22.dll!scm_catch_with_pre_unwind_handler+0x4e
32, libguile-2.0-22.dll!scm_i_with_continuation_barrier+0x6f
33, libguile-2.0-22.dll!scm_current_error_port+0x20
34, guile.exe+0x86d90
0, ntoskrnl.exe!_misaligned_access+0x17e7
1, ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x93d
2, ntoskrnl.exe!KeWaitForSingleObject+0x19f
3, ntoskrnl.exe!_misaligned_access+0xba4
4, ntoskrnl.exe!_misaligned_access+0x1821
5, ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x93d
6, ntoskrnl.exe!KeWaitForSingleObject+0x19f
7, ntoskrnl.exe!NtWaitForSingleObject+0xde
8, ntoskrnl.exe!KeSynchronizeExecution+0x3a23
9, wow64cpu.dll!TurboDispatchJumpAddressEnd+0x6c0
10, wow64cpu.dll!TurboDispatchJumpAddressEnd+0x4a8
11, wow64.dll!Wow64SystemServiceEx+0x1ce
12, wow64.dll!Wow64LdrpInitialize+0x429
13, ntdll.dll!RtlIsDosDeviceName_U+0x24c87
14, ntdll.dll!LdrInitializeThunk+0xe
15, ntdll.dll!ZwWaitForSingleObject+0x15
16, kernel32.dll!WaitForSingleObjectEx+0x43
17, kernel32.dll!WaitForSingleObject+0x12
18, libwinpthread-1.dll!pthread_cond_init+0x26f
19, kernel32.dll!WaitForSingleObject+0x12
20, libwinpthread-1.dll!pthread_rel_time_in_ms+0x24a
21, libwinpthread-1.dll!pthread_mutex_init+0x29b
22, libwinpthread-1.dll!pthread_rel_time_in_ms+0x24a
23, libgc-1.dll!GC_call_with_gc_active+0x216
24, libwinpthread-1.dll!pthread_mutex_trylock+0x1f
25, libgc-1.dll!GC_pthread_detach+0x28
26, libwinpthread-1.dll!pthread_self+0x8
27, libguile-2.0-22.dll!scm_all_threads+0x126
28, libwinpthread-1.dll!pthread_getclean+0x8
29, libgc-1.dll!GC_use_threads_discovery+0x26e
30, libgc-1.dll!GC_call_with_stack_base+0x1c
31, msvcrt.dll!itow_s+0x4c
32, msvcrt.dll!endthreadex+0x6c
33, kernel32.dll!BaseThreadInitThunk+0x12
34, ntdll.dll!RtlInitializeExceptionChain+0x63
35, ntdll.dll!RtlInitializeExceptionChain+0x36
<LRN> if i insert (display "Hello\n") into top-repl, it prints there (at
least at the beginning of the function). Nothing is printed in
start-repl [12:47]
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#14171: Aw: Re: bug#14171: REPL doesn't work on windows min-gw
2013-04-11 14:40 ` bug#14171: Aw: " Jan Schukat
2013-04-14 17:26 ` Mark H Weaver
@ 2013-04-15 6:37 ` Jan Schukat
2016-06-20 20:28 ` Andy Wingo
1 sibling, 1 reply; 6+ messages in thread
From: Jan Schukat @ 2013-04-15 6:37 UTC (permalink / raw)
To: Andy Wingo; +Cc: 14171
[-- Attachment #1: Type: text/plain, Size: 7212 bytes --]
Just a quick follow-up. Tried to run the test suite. And to see how it
is supposed to work I first did that on linux. But when you use a
--disaple-posix guile it fails at the second test already because chdir
is defined in the posix module. So I didn't even run it on windows yet.
Here's my output:
;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0
;;; or pass the --no-auto-compile argument to disable.
;;; compiling /home/shookie/core/lib/guile-2.0/test-suite/guile-test
;;; compiling /home/shookie/core/lib/guile-2.0/test-suite/test-suite/lib.scm
;;; test-suite/lib.scm:531:46: warning: possibly unbound variable
`setlocale'
;;; test-suite/lib.scm:531:46: warning: possibly unbound variable `LC_ALL'
;;; test-suite/lib.scm:533:49: warning: possibly unbound variable
`setlocale'
;;; test-suite/lib.scm:533:49: warning: possibly unbound variable `LC_ALL'
;;; test-suite/lib.scm:539:14: warning: possibly unbound variable
`setlocale'
;;; test-suite/lib.scm:539:14: warning: possibly unbound variable `LC_ALL'
;;; compiled
/home/shookie/.cache/guile/ccache/2.0-LE-4-2.0/home/shookie/core/lib/guile-2.0/test-suite/test-suite/lib.scm.go
;;; guile-test:250:20: warning: possibly unbound variable `close'
;;; compiled
/home/shookie/.cache/guile/ccache/2.0-LE-4-2.0/home/shookie/core/lib/guile-2.0/test-suite/guile-test.go
Running tests/00-initial-env.test
;;; compiling
/home/shookie/core/lib/guile-2.0/test-suite/tests/00-initial-env.test
;;; compiled
/home/shookie/.cache/guile/ccache/2.0-LE-4-2.0/home/shookie/core/lib/guile-2.0/test-suite/tests/00-initial-env.test.go
Running tests/00-socket.test
;;; compiling
/home/shookie/core/lib/guile-2.0/test-suite/tests/00-socket.test
;;; tests/00-socket.test:195:0: warning: possibly unbound variable `chdir'
;;; tests/00-socket.test:303:23: warning: possibly unbound variable
`primitive-fork'
;;; tests/00-socket.test:338:33: warning: possibly unbound variable
`waitpid'
;;; tests/00-socket.test:339:24: warning: possibly unbound variable
`status:exit-val'
;;; tests/00-socket.test:383:23: warning: possibly unbound variable
`primitive-fork'
;;; tests/00-socket.test:411:33: warning: possibly unbound variable
`waitpid'
;;; tests/00-socket.test:412:24: warning: possibly unbound variable
`status:exit-val'
;;; tests/00-socket.test:481:23: warning: possibly unbound variable
`primitive-fork'
;;; tests/00-socket.test:516:33: warning: possibly unbound variable
`waitpid'
;;; tests/00-socket.test:517:24: warning: possibly unbound variable
`status:exit-val'
;;; tests/00-socket.test:522:20: warning: possibly unbound variable `chdir'
;;; compiled
/home/shookie/.cache/guile/ccache/2.0-LE-4-2.0/home/shookie/core/lib/guile-2.0/test-suite/tests/00-socket.test.go
Backtrace:
In ice-9/boot-9.scm:
157: 10 [catch #t #<catch-closure 9515ae0> ...]
In unknown file:
?: 9 [apply-smob/1 #<catch-closure 9515ae0>]
In ice-9/boot-9.scm:
63: 8 [call-with-prompt prompt0 ...]
In ice-9/eval.scm:
432: 7 [eval # #]
In guile-test:
240: 6 [main ("guile-test")]
In ice-9/boot-9.scm:
697: 5 [for-each #<procedure 9b1d490 at guile-test:240:29 (test)> #]
In test-suite/lib.scm:
459: 4 [with-test-prefix* "tests/00-socket.test" ...]
In ice-9/boot-9.scm:
2320: 3 [save-module-excursion #<procedure 9b62d40 at
ice-9/boot-9.scm:3961:3 ()>]
3966: 2 [#<procedure 9b62d40 at ice-9/boot-9.scm:3961:3 ()>]
In unknown file:
?: 1 [load-compiled/vm
"/home/shookie/.cache/guile/ccache/2.0-LE-4-2.0/home/shookie/core/lib/guile-2.0/test-suite/tests/00-socket.test.go"]
In tests/00-socket.test:
195: 0 [#<procedure 9b0ab80 ()>]
tests/00-socket.test:195:0: In procedure #<procedure 9b0ab80 ()>:
tests/00-socket.test:195:0: In procedure module-lookup: Unbound
variable: chdir
and the guile.log:
PASS: tests/00-initial-env.test: goopsless: + wrong type argument: 1st
argument string (eval)
PASS: tests/00-initial-env.test: goopsless: + wrong type argument: 1st
argument string (compile)
PASS: tests/00-initial-env.test: goopsless: + wrong type argument: 2nd
argument bool (eval)
PASS: tests/00-initial-env.test: goopsless: + wrong type argument: 2nd
argument bool (compile)
PASS: tests/00-initial-env.test: goopsless: + wrong type argument:
implicit forcing is not supported (eval)
PASS: tests/00-initial-env.test: goopsless: + wrong type argument:
implicit forcing is not supported (compile)
PASS: tests/00-initial-env.test: goopsless: - wrong type argument: 1st
argument string (eval)
PASS: tests/00-initial-env.test: goopsless: - wrong type argument: 1st
argument string (compile)
PASS: tests/00-initial-env.test: goopsless: - wrong type argument: 2nd
argument symbol (eval)
PASS: tests/00-initial-env.test: goopsless: - wrong type argument: 2nd
argument symbol (compile)
PASS: tests/00-socket.test: htonl: 0
PASS: tests/00-socket.test: htonl: -1
PASS: tests/00-socket.test: htonl: 2^32
PASS: tests/00-socket.test: htonl: 2^1024
PASS: tests/00-socket.test: inet-ntop: ipv6: 0
PASS: tests/00-socket.test: inet-ntop: ipv6: 2^128-1
PASS: tests/00-socket.test: inet-ntop: ipv6: -1
PASS: tests/00-socket.test: inet-ntop: ipv6: 2^128
PASS: tests/00-socket.test: inet-ntop: ipv6: 2^1024
PASS: tests/00-socket.test: inet-pton: ipv6: 00:00:00:00:00:00:00:00
PASS: tests/00-socket.test: inet-pton: ipv6: 0:0:0:0:0:0:0:1
PASS: tests/00-socket.test: inet-pton: ipv6: ::1
PASS: tests/00-socket.test: inet-pton: ipv6:
FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF
PASS: tests/00-socket.test: inet-pton: ipv6:
F000:0000:0000:0000:0000:0000:0000:0000
PASS: tests/00-socket.test: inet-pton: ipv6:
0F00:0000:0000:0000:0000:0000:0000:0000
PASS: tests/00-socket.test: inet-pton: ipv6:
0000:0000:0000:0000:0000:0000:0000:00F0
PASS: tests/00-socket.test: inet-ntop: ipv4: 127.0.0.1
PASS: tests/00-socket.test: inet-ntop: ipv6:
FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF
PASS: tests/00-socket.test: inet-ntop: ipv6: ::1
PASS: tests/00-socket.test: make-socket-address: AF_INET
PASS: tests/00-socket.test: make-socket-address: AF_INET6
PASS: tests/00-socket.test: make-socket-address: AF_UNIX
PASS: tests/00-socket.test: ntohl: 0
PASS: tests/00-socket.test: ntohl: -1
PASS: tests/00-socket.test: ntohl: 2^32
PASS: tests/00-socket.test: ntohl: 2^1024
Regards
Jan Schukat
On 04/11/2013 04:40 PM, Jan Schukat wrote:
> Ok, did use this package: guile-2.0.9.2-f480a-dirty.tar.gz and can
> build and run guile-2.0 on mingw when I --disable-posix, which makes
> sense, since Windows is not posix :) Can even use threads.
> I guess I try to get the test-suite to run now.
> I'm pretty happy now that my issues on windows could be resolved in
> the last few weeks.
> Regards
> Jan Schukat
> *Gesendet:* Mittwoch, 10. April 2013 um 22:23 Uhr
> *Von:* "Andy Wingo" <wingo@pobox.com>
> *An:* "Jan Schukat" <shookie@email.de>
> *Cc:* 14171@debbugs.gnu.org
> *Betreff:* Re: bug#14171: REPL doesn't work on windows min-gw
> On Wed 10 Apr 2013 05:59, "Jan Schukat" <shookie@email.de> writes:
>
> > system/repl/common.scm:147:25: In procedure make-repl:
> > system/repl/common.scm:147:25: In procedure module-lookup: Unbound
> > variable: times
>
> Can you try with the 2.0.9 release, made yesterday? It should fix this
> error.
>
> Andy
> --
> http://wingolog.org/
[-- Attachment #2: Type: text/html, Size: 10450 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#14171: Aw: Re: bug#14171: REPL doesn't work on windows min-gw
2013-04-15 6:37 ` Jan Schukat
@ 2016-06-20 20:28 ` Andy Wingo
0 siblings, 0 replies; 6+ messages in thread
From: Andy Wingo @ 2016-06-20 20:28 UTC (permalink / raw)
To: Jan Schukat; +Cc: 14171-done
Hi,
Expiring this old bug. I understand that things are working better on
MinGW these days but if you find a new problem with Guile 2.0.11 or the
stable-2.0 branch, please file a new bug. Cheers :)
Andy
On Mon 15 Apr 2013 08:37, Jan Schukat <shookie@email.de> writes:
> Just a quick follow-up. Tried to run the test suite. And to see how it
> is supposed to work I first did that on linux. But when you use a -
> -disaple-posix guile it fails at the second test already because chdir
> is defined in the posix module. So I didn't even run it on windows
> yet.
>
> Here's my output:
>
> ;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0
> ;;; or pass the --no-auto-compile argument to disable.
> ;;; compiling /home/shookie/core/lib/guile-2.0/test-suite/guile-test
> ;;; compiling
> /home/shookie/core/lib/guile-2.0/test-suite/test-suite/lib.scm
> ;;; test-suite/lib.scm:531:46: warning: possibly unbound variable
> `setlocale'
> ;;; test-suite/lib.scm:531:46: warning: possibly unbound variable
> `LC_ALL'
> ;;; test-suite/lib.scm:533:49: warning: possibly unbound variable
> `setlocale'
> ;;; test-suite/lib.scm:533:49: warning: possibly unbound variable
> `LC_ALL'
> ;;; test-suite/lib.scm:539:14: warning: possibly unbound variable
> `setlocale'
> ;;; test-suite/lib.scm:539:14: warning: possibly unbound variable
> `LC_ALL'
> ;;; compiled
> /home/shookie/.cache/guile/ccache/2.0-LE-4-2.0/home/shookie/core/lib/guile-2.0/test-suite/test-suite/lib.scm.go
> ;;; guile-test:250:20: warning: possibly unbound variable `close'
> ;;; compiled
> /home/shookie/.cache/guile/ccache/2.0-LE-4-2.0/home/shookie/core/lib/guile-2.0/test-suite/guile-test.go
> Running tests/00-initial-env.test
> ;;; compiling
> /home/shookie/core/lib/guile-2.0/test-suite/tests/00-initial-env.test
> ;;; compiled
> /home/shookie/.cache/guile/ccache/2.0-LE-4-2.0/home/shookie/core/lib/guile-2.0/test-suite/tests/00-initial-env.test.go
> Running tests/00-socket.test
> ;;; compiling
> /home/shookie/core/lib/guile-2.0/test-suite/tests/00-socket.test
> ;;; tests/00-socket.test:195:0: warning: possibly unbound variable
> `chdir'
> ;;; tests/00-socket.test:303:23: warning: possibly unbound variable
> `primitive-fork'
> ;;; tests/00-socket.test:338:33: warning: possibly unbound variable
> `waitpid'
> ;;; tests/00-socket.test:339:24: warning: possibly unbound variable
> `status:exit-val'
> ;;; tests/00-socket.test:383:23: warning: possibly unbound variable
> `primitive-fork'
> ;;; tests/00-socket.test:411:33: warning: possibly unbound variable
> `waitpid'
> ;;; tests/00-socket.test:412:24: warning: possibly unbound variable
> `status:exit-val'
> ;;; tests/00-socket.test:481:23: warning: possibly unbound variable
> `primitive-fork'
> ;;; tests/00-socket.test:516:33: warning: possibly unbound variable
> `waitpid'
> ;;; tests/00-socket.test:517:24: warning: possibly unbound variable
> `status:exit-val'
> ;;; tests/00-socket.test:522:20: warning: possibly unbound variable
> `chdir'
> ;;; compiled
> /home/shookie/.cache/guile/ccache/2.0-LE-4-2.0/home/shookie/core/lib/guile-2.0/test-suite/tests/00-socket.test.go
> Backtrace:
> In ice-9/boot-9.scm:
> 157: 10 [catch #t #<catch-closure 9515ae0> ...]
> In unknown file:
> ?: 9 [apply-smob/1 #<catch-closure 9515ae0>]
> In ice-9/boot-9.scm:
> 63: 8 [call-with-prompt prompt0 ...]
> In ice-9/eval.scm:
> 432: 7 [eval # #]
> In guile-test:
> 240: 6 [main ("guile-test")]
> In ice-9/boot-9.scm:
> 697: 5 [for-each #<procedure 9b1d490 at guile-test:240:29 (test)> #]
> In test-suite/lib.scm:
> 459: 4 [with-test-prefix* "tests/00-socket.test" ...]
> In ice-9/boot-9.scm:
> 2320: 3 [save-module-excursion #<procedure 9b62d40 at
> ice-9/boot-9.scm:3961:3 ()>]
> 3966: 2 [#<procedure 9b62d40 at ice-9/boot-9.scm:3961:3 ()>]
> In unknown file:
> ?: 1 [load-compiled/vm
> "/home/shookie/.cache/guile/ccache/2.0-LE-4-2.0/home/shookie/core/lib/guile-2.0/test-suite/tests/00-socket.test.go"]
> In tests/00-socket.test:
> 195: 0 [#<procedure 9b0ab80 ()>]
>
> tests/00-socket.test:195:0: In procedure #<procedure 9b0ab80 ()>:
> tests/00-socket.test:195:0: In procedure module-lookup: Unbound
> variable: chdir
>
> and the guile.log:
>
> PASS: tests/00-initial-env.test: goopsless: + wrong type argument: 1st
> argument string (eval)
> PASS: tests/00-initial-env.test: goopsless: + wrong type argument: 1st
> argument string (compile)
> PASS: tests/00-initial-env.test: goopsless: + wrong type argument: 2nd
> argument bool (eval)
> PASS: tests/00-initial-env.test: goopsless: + wrong type argument: 2nd
> argument bool (compile)
> PASS: tests/00-initial-env.test: goopsless: + wrong type argument:
> implicit forcing is not supported (eval)
> PASS: tests/00-initial-env.test: goopsless: + wrong type argument:
> implicit forcing is not supported (compile)
> PASS: tests/00-initial-env.test: goopsless: - wrong type argument: 1st
> argument string (eval)
> PASS: tests/00-initial-env.test: goopsless: - wrong type argument: 1st
> argument string (compile)
> PASS: tests/00-initial-env.test: goopsless: - wrong type argument: 2nd
> argument symbol (eval)
> PASS: tests/00-initial-env.test: goopsless: - wrong type argument: 2nd
> argument symbol (compile)
> PASS: tests/00-socket.test: htonl: 0
> PASS: tests/00-socket.test: htonl: -1
> PASS: tests/00-socket.test: htonl: 2^32
> PASS: tests/00-socket.test: htonl: 2^1024
> PASS: tests/00-socket.test: inet-ntop: ipv6: 0
> PASS: tests/00-socket.test: inet-ntop: ipv6: 2^128-1
> PASS: tests/00-socket.test: inet-ntop: ipv6: -1
> PASS: tests/00-socket.test: inet-ntop: ipv6: 2^128
> PASS: tests/00-socket.test: inet-ntop: ipv6: 2^1024
> PASS: tests/00-socket.test: inet-pton: ipv6: 00:00:00:00:00:00:00:00
> PASS: tests/00-socket.test: inet-pton: ipv6: 0:0:0:0:0:0:0:1
> PASS: tests/00-socket.test: inet-pton: ipv6: ::1
> PASS: tests/00-socket.test: inet-pton: ipv6:
> FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF
> PASS: tests/00-socket.test: inet-pton: ipv6:
> F000:0000:0000:0000:0000:0000:0000:0000
> PASS: tests/00-socket.test: inet-pton: ipv6:
> 0F00:0000:0000:0000:0000:0000:0000:0000
> PASS: tests/00-socket.test: inet-pton: ipv6:
> 0000:0000:0000:0000:0000:0000:0000:00F0
> PASS: tests/00-socket.test: inet-ntop: ipv4: 127.0.0.1
> PASS: tests/00-socket.test: inet-ntop: ipv6:
> FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF
> PASS: tests/00-socket.test: inet-ntop: ipv6: ::1
> PASS: tests/00-socket.test: make-socket-address: AF_INET
> PASS: tests/00-socket.test: make-socket-address: AF_INET6
> PASS: tests/00-socket.test: make-socket-address: AF_UNIX
> PASS: tests/00-socket.test: ntohl: 0
> PASS: tests/00-socket.test: ntohl: -1
> PASS: tests/00-socket.test: ntohl: 2^32
> PASS: tests/00-socket.test: ntohl: 2^1024
>
> Regards
>
> Jan Schukat
>
> On 04/11/2013 04:40 PM, Jan Schukat wrote:
>
>
>
> Ok, did use this package: guile-2.0.9.2-f480a-dirty.tar.gz and can
> build and run guile-2.0 on mingw when I --disable-posix, which
> makes sense, since Windows is not posix :) Can even use threads.
>
> I guess I try to get the test-suite to run now.
>
> I'm pretty happy now that my issues on windows could be resolved
> in the last few weeks.
>
> Regards
>
> Jan Schukat
>
>
>
> Gesendet: Mittwoch, 10. April 2013 um 22:23 Uhr
> Von: "Andy Wingo" <wingo@pobox.com>
> An: "Jan Schukat" <shookie@email.de>
> Cc: 14171@debbugs.gnu.org
> Betreff: Re: bug#14171: REPL doesn't work on windows min-gw
> On Wed 10 Apr 2013 05:59, "Jan Schukat" <shookie@email.de> writes:
>
> > system/repl/common.scm:147:25: In procedure make-repl:
> > system/repl/common.scm:147:25: In procedure module-lookup:
> Unbound
> > variable: times
>
> Can you try with the 2.0.9 release, made yesterday? It should fix
> this
> error.
>
> Andy
> --
> http://wingolog.org/
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2016-06-20 20:28 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-04-10 3:59 bug#14171: REPL doesn't work on windows min-gw Jan Schukat
2013-04-10 20:23 ` Andy Wingo
2013-04-11 14:40 ` bug#14171: Aw: " Jan Schukat
2013-04-14 17:26 ` Mark H Weaver
2013-04-15 6:37 ` Jan Schukat
2016-06-20 20:28 ` Andy Wingo
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).