guile-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: guile 2.0.9 build on mingw


From: Ludovic Courtès
Subject: Re: guile 2.0.9 build on mingw
Date: Sun, 16 Jun 2013 16:59:19 +0200
User-agent: Gnus/5.130007 (Ma Gnus v0.7) Emacs/24.3 (gnu/linux)

Eli Zaretskii <address@hidden> skribis:

> A few strange warnings and failures I saw while running the test
> suite, which I couldn't figure out or couldn't find a solution for:
>
> 1. Even after using -export-dynamic, the tests in foreign.test which
>    use 'qsort' fail:

See my other message.

> 2. Failures in ports.test:
>
>      Running ports.test
>      FAIL: ports.test: file: binary mode ignores port encoding
>      FAIL: ports.test: file: binary mode ignores file coding declaration
>
>    Should I worry about this?

Possibly.  :-)

Can you try this patch, run ./check-guile ports.test, and report the
debugging statements that are printed?

diff --git a/test-suite/tests/ports.test b/test-suite/tests/ports.test
index 9b1c6c0..6137181 100644
--- a/test-suite/tests/ports.test
+++ b/test-suite/tests/ports.test
@@ -251,7 +251,7 @@
                         (line (read-line in-port)))
                    (close-port in-port)
                    (delete-file filename)
-                   (string=? line binary-test-string)))))
+                   (string=? (pk 'line line) binary-test-string)))))
 
 ;;; binary mode ignores file coding declaration
 (pass-if "file: binary mode ignores file coding declaration"
@@ -272,7 +272,7 @@
                         (line2 (read-line in-port)))
                    (close-port in-port)
                    (delete-file filename)
-                   (string=? line2 binary-test-string)))))
+                   (string=? (pk 'line2 line2) binary-test-string)))))
 
 ;; open-file ignores file coding declaration by default
 (pass-if "file: open-file ignores coding declaration by default"
> 3. Emacs-lisp test display warnings about overriding Scheme procedures
>    -- is that something to worry about?

No.

Thanks,
Ludo’.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]