gmane.lisp.guile.user

Re: Extending a GTK+ Application with Guile

Ludovic Courtès — 2012-05-25T14:30:44

Hi!

Kevin J. Fletcher <dev< at >kjfletch.co.uk> skribis:


Sounds good at first sight.  In fact, you could look at (system repl
server), which implements something like that.  That’s what the
‘--listen’ command-line option uses.


Actually, ‘,q’ does ‘exit’, which just throws an exception, so it’s
harmless (you can check it with ‘--listen’: typing ,q in the REPL over
telnet doesn’t terminate the process, it just terminates the REPL
server.)

But then of course, if the user calls ‘primitive-exit’ or similar, the
whole process terminates.  You could rebind ‘primitive-exit’ to
something harmless, but I’m not convince that protecting users against
themselves makes sense.


It’s supposed to build and run with MinGW, though it’s definitely not
widely tested.

Thanks,
Ludo’.

Re: Extending a GTK+ Application with Guile

Paul Emsley — 2012-05-25T11:14:54

Very good.  That is what I do with Coot.


Bleugh!


Yes.


By "at the same time" do you mean in "a different thread"?

If so, don't do that.

I use scm_shell() but only for command-line/non-gtk-graphics mode.
To interact with guile I use guile-gui.


It is not clear to me that you need VTE and threads.

I have my guile-scripts/functions (well, 99% of them) run in the 
main/gtk thread - many using timeout functions.


My understanding is that it is possible, but non-trivial.  We have not 
made a guile-enabled Coot on Windows (yet).

HTH,

Paul.

Extending a GTK+ Application with Guile

Kevin J. Fletcher — 2012-05-24T19:11:50

Hello Guilers.

I'm currently writing some prototype code before starting a project and
have a few questions that I hope some of you may be able to answer.

My intent is to add guile as a method of [optionally, at build time]
extending a GTK+ application. With the addition of being able to run
guile scripts I hope to provide a guile-shell to give real-time
interactive power. First a question of program architecture;

As the guile extensions are optional I run GTK on a main thread and the
shell on a second pthread. I connect the shell through a PTY to the
virtual terminal widget.

I apologise to those with mail clients not using monospace fonts.

  THREAD1            THREAD2
 ---------           -------
| GTK     |   pty   | guile |
|     VTE |<------->| shell |
|  -----  |          -------
| guile   |
|  scripts|
 ---------

0) Is there anything wrong with this architecture?

   a) Is it valid to use both scm_shell and other guile code at the same
   time or is scm_shell designed to run in isolation?

   b) Not related to guile but while I'm here I may as well ask. Is there
   a more appropriate GTK+ method of communicating (STDIN, STDOUT,
   STERR) with the running application (to replace the VTE above)

1) scm_shell allows the `,q' command (and probably some other exit
routes) which kills the whole application. Is there a way to present a
shell (or similar subset) without the ability to exit?

2) Thinking of portability, is guile running on Windows (without
cygwin), to justify the claim of 'ubiquitous'?

Happy Hacking,
Kevin Fletcher.

Re: letter occurence in a text

gregory benison — 2012-05-23T13:57:38

Why store the alist keys as one-character strings, rather than just as
characters?  Storing as characters would be simpler:

;; Given an alist 'lst' containing character counts and character 'c',
;; return an alist with the count of 'c' incremented (set to 1 if it
doesn't exist).
(define (lettre-test c lst)
  (let ((current (assoc-ref lst c)))
     (assoc-set! lst c (+ 1 (or current 0)))))

Character frequency analysis can be performed with a "fold" operation:

((#\! . 1)
 (#\d . 1)
 (#\r . 1)
 (#\w . 1)
 (#\space . 1)
 (#\, . 1)
 (#\o . 2)
 (#\l . 3)
 (#\e . 1)
 (#\h . 1))

I think it would be best to separate the filtering for alphabetic
chars from the "lettre-test" function; they're separate ideas:

((#\d . 1)
 (#\r . 1)
 (#\w . 1)
 (#\o . 2)
 (#\l . 3)
 (#\e . 1)
 (#\h . 1))

The drawback of this solution, as currently written, is that it can't
lazily read a file; you'd have to read the entire file into a string
first.  It should be possible to modify this to use streams rather
than lists, though.

Re: letter occurence in a text

Mark Skilbeck — 2012-05-22T23:57:01

Hi!

I did a short frequency-analysis function some time ago and after a
little digging found it. With a little haqqing you could modify it to
your needs:

(code)
;; Frequency analysis. Not Frequently Analed.

(define (frequency-analysis text)
  (if (null? text)
      '()
      (let loop ((table (list (cons (car text) 1)))
                 (text (cdr text)))
        (cond ((null? text) table)
              ((not (assoc (car text) table))
               (loop (append table
                             (list (cons (car text) 1)))
                     (cdr text)))
              (else
               (set-cdr! (assoc (car text) table)
                         (+ (cdr (assoc (car text) table)) 1))
               (loop table (cdr text)))))))
(/code)

I should probably talk you through the code. But, if think it's simple
enough and I am drunk enough not to require it!

Good day!

- mgsk.

letter occurence in a text

nrichard — 2012-05-22T14:26:09

hello my problem is to count occurence of letter in a text and come out with
an assoc-list like
'((a.16) (b.10) ... (z.5))
i started a fee function but they don't work so please help me

;; an alist
(define lettre '((""."") ) )
(define lettre2 '(("a". 1) ("b". 1) ("c". 1) ) )

;; this function take a key and an alist
;; add the key to the alist if it is not a space,a newline,and does not
already exist
;; update the value of the given key
(define (lettre-test x alist)
(cond ((and 
          ( and (not (char=?  x #\space))(not (char=?  x #\newline)))   
          (eq? (assoc (make-string 1 x) alist) #f))  
          (set! alist
          (assoc-set! alist (make-string 1 x) 0 )))
          ((char=?  x #\space) '())
          ((char=?  x #\newline) '()) 
           (else
           (set! alist   
       (assoc-set! alist (make-string 1 x) (+ (assoc-ref alist
(make-string 1 x)) 1))))))

;; this function open a file
;; read the caracter and count the occurence of each character
(define (compte-char source alist)
(let ((p (open-port source)))
  (let f ((x (read-char p)))
    (cond ((eof-object? x)
        (begin
          (close-input-port p)
          '()))        
         (else
        (cons (lettre-test x alist) (f (read-char p))))))))

Re: guile-lib test failed

Andy Wingo — 2012-05-21T09:05:05


A segmentation fault!  This is bad.

Can you run "ulimit -c unlimited" to enable core dumps, then try again,
then "gdb /usr/local/bin/guile core" (assuming the core file is there;
if not, check your /proc/sys/kernel/core_pattern), then "thr apply all
bt full".

Thanks!

Andy

guile-lib test failed

Germán A. Arias — 2012-05-20T12:31:50

With guile 2.0.5 installing guile-lib 0.2.1 ./configure and make
run without problems. But "make check" say one test failed. See
attached file. There are some spanish messages. I don't know how
configure it to display all in english. Regards.

Re: dynamic ffi and C struct

Nala Ginrut — 2012-05-20T03:40:35

And if you want to dereference the returned struct pointer, use parse-c-struct
say, there's a returned C struct like:
aa { (int)1 ,(int)2 }

you may convert it to list like this:
(parse-c-struct aa (list int int))
==> (1 2)

Then the rest is list operation, has no part in C.


On Sun, May 20, 2012 at 8:45 AM, Mark H Weaver <mhw< at >netris.org> wrote:

Re: dynamic ffi and C struct

Mark H Weaver — 2012-05-20T00:45:44

Although it is not documented in the manual, I see from the source code
that a C struct parameter can be specified using a nested list in the
foreign type passed to 'pointer->procedure'.


For this example, there's an additional complication of the inline array
within the struct, which is not supported by libffi, upon which Guile's
dynamic FFI is based.  I'm not an expert on this subject, but I strongly
suspect that on most (if not all) platforms, the struct above has the
same layout as the following one:

  typedef struct {
    int dat_0;
    int dat_1;
  } foo_t;

Assuming this is the case, here's one way to wrap 'func':

  (use-modules (system foreign))

  (define foo-library-obj (dynamic-link "libfoo"))
  (define foo-struct-type (list int int))
  
  (define (make-foo-struct dat-0 dat-1)
    (make-c-struct foo-struct-type (list dat-0 dat-1)))
  
  (define func
    (pointer->procedure int
                        (dynamic-func "func" foo-library-obj)
                        (list foo-struct-type)))

and here's an example of how to use it:

  (func (make-foo-struct 4 5))

It is also possible to wrap C functions that return structs, by passing
a list to the first parameter of 'pointer->procedure', and then using
'parse-c-struct' to extract the fields of the returned struct.

Hope this helps!

    Mark

dynamic ffi and C struct

cong gu — 2012-05-19T11:32:07

Hello,

Is it possible to use the current dynamic ffi to call a C function
whose parameter is a C struct (not a pointer to a C struct) ?

I cannot find much about it in the documentation.  After a brief look
at the source of foreign.c of guile, I found guile actually does some
parsing of nested argument list for `pointer->procedure' and generates
compound ffi types.  But I don't know the right data structure to give
when actually calling the foreign function.

For example, what should I do for the following function?

typedef struct {
  int dat[2];
} foo_t;

int func ( foo_t arg );

Re: SRFI-64 module and SRFI-78 module -- archive file attached

Sunjoong Lee — 2012-05-14T14:07:13

URL changed:

SRFI 64: "A Scheme API for test suites by Per Bothner" Guile implementation
-
https://gitorious.org/srfi-64-port/srfi-64-guile

SRFI 78: "Lightweight testing by Sebastian Egner" Guile module -
https://gitorious.org/srfi-78-guile

Test code added:
Modified test suite for the testing SRFI 64 to use (test-suite lib) module
of Guile source archive -
https://gitorious.org/srfi-64-port/srfi-64-guile/blobs/master/test-suite/tests/srfi-64.test

Re: http-post

Noah Lavine — 2012-05-10T02:22:03

Hello,


Yes, I like that idea. At least our procedures will be consistent with
themselves. :-)

You shouldn't work too hard writing tests for code that you didn't
write, but it sounds like the best way to test your code is to feed
its results to the web server.

Thanks for working on this,
Noah

RE: guile-gnome-platform 2.16.2 released

Sunjoong Lee — 2012-05-09T23:57:55

Hello,

I'm glad to hear guile-gnome-platform works with Guile 2.0. To celebrate
it, I've attatched my ebuild files for Gentoo Linux users. You
know, Gentoo's last stable guile ebuild file is guile-1.8.8-r1.ebuild for
Guile 1.8.8 but the last stable version of Guile itself is 2.0.5. There
are guile-2.0.5.ebuild, g-wrap-1.9.14.ebuild
and guile-gnome-platform-2.16.2.ebuild in my attatched file. You need
a ebuild file for guile-lib 0.1.9 but it is in your default portage tree.
If not so, sync your portage tree; "emerge --sync".

0. Update your system:
    # emerge --sync
    # emerge -uND world
    # emerge --depclean
    # revdep-rebuild

1. Put new ebuild files in your local portage overlay tree:
    # cp guile-gnome-platform-ebuild.tar.gz /usr/local
    # cd /usr/local
    # tar xvjf guile-gnome-platform-ebuild.tar.gz
    # rm guile-gnome-platform-ebuild.tar.gz

2. Check your PORTDIR_OVERLAY environment variable in /etc/make.conf file.
I assume that:
    $ grep PORTDIR_OVERLAY /etc/make.conf
    PORTDIR_OVERLAY="/usr/local/portage"

3. Use ~x86 keyword in your Gentoo keyword file:
    # vi /etc/portage/package.keywords
    The contents of keyword file is:
    dev-libs/g-wrap ~x86
    dev-scheme/guile ~x86
    dev-scheme/guile-gnome-platform ~x86
    dev-scheme/guile-lib ~x86

4. Uninstall guile 1.8.8 if you had installed it:
    # emerge -C guile

5. Install guile-gnome-platform; emerge script will
install guile, guile-lib and g-wrap for guile-gnome-platform:
    # emerge guile-gnome-platform
    # emerge --depclean
    # revdep-rebuild

2012/5/9 Andy Wingo <wingo< at >pobox.com>

[ANN] Guile-Reader 0.6

Ludovic Courtès — 2012-05-08T21:06:42

Version 0.6 of Guile-Reader for Guile 2.0.x and 1.8.x is now available.
This release adds new features, most notably Guile 2.0 and Unicode support.

  http://dl.sv.nongnu.org/releases/guile-reader/guile-reader-0.6.tar.gz
  http://dl.sv.nongnu.org/releases/guile-reader/guile-reader-0.6.tar.gz.sig

SHA1 sums:

  aaedfe0c656775ba895b02293481a7d7c36b1f7e  guile-reader-0.6.tar.gz
  284404e6403d396819ff4e060d4a496f66727d8f  guile-reader-0.6.tar.gz.sig

Documentation is available from:

  http://www.nongnu.org/guile-reader/

Guile-Reader is a reader creation framework for Guile.  It can be
thought of as an alternative to Guile's built-in reader.  The purpose of
Guile-Reader is to allow for the creation of readers for different
variants of the Scheme/Lisp syntax.  Its design allows the re-use and
composition of various parts of a lexer called “token readers”.  It
comes with a library of re-usable token readers that can be used to
build a Scheme reader with various extensions.  For instance, syntax
extensions for DSSSL keywords, SRFI-30 block comments, SRFI-62 S-exp
comments, square-bracket S-exps, and brace S-exps are provided and
readily usable through the ‘make-alternate-guile-reader’ procedure.

Additionally, Guile-Reader aims to improve on Guile's reader sub-system
by allowing for the coexistence of several, potentially incompatible,
readers within a single Guile program.  In particular, it provides a
“confinement” mechanism that confines changes made via ‘read-set!’ and
‘read-hash-extend’ to the calling module.

New in Guile-Reader 0.6

  * Guile-Reader is now distributed under GPLv3 or later (instead of
    GPLv2 or later).

  * New token reader for R6RS-style syntax quotes: #', #`, and #,.

  * `make-guile-reader' returns a reader that understands SRFI-62
    s-exp comments, R6RS-style syntax quotes, and s-exps introduced by
    square brackets.  All these are supported by default by `read' in
    Guile 2.0.

  * On Guile 2.0, non-ASCII Unicode symbols, strings, characters, and
    Skribe-expressions are correctly read.

  * On Guile 2.0, Scheme source files are compiled and installed.

  * Bugs fixed

    * Add support for rationals in the number token reader.

    * Provide replacement for some `scm_i_' functions and other
      internals no longer accessible in Guile 1.9+.

    * Adjust packaging so that it works with Guile 1.9+.

Ludovic.

Re: Working http-get example and still unsolved problem

Ian Price — 2012-05-07T20:09:40

Well, I mentioned it in the thread where I posted the patch, but to
briefly summarise

(define a <port>)
(define b (make-chunked-input-port a))
(close-port b)

What is the state of a?

(define c <port>)
(define d (make-chunked-output-port c))
(close-port d)

Likewise for c.

If you take, say, Java's BufferedReader, when the BufferedReader is
closed, it also closes the underlying Reader. This behaviour is
convenient, as you layer ports on top of one another, you only need to
worry about closing the top-most one. Since chunked transfer encoding is
only one of the possible encodings for http requests (though the only
one required by HTTP 1.1), it is possible that we would eventually want
to layer, say, gzip on top of chunked transfer encoding ports.

The issue with having this behaviour, is that while propagating the
close may be necessary to ensure proper behaviour, we don't necessarily
want to close the original socket. In particular, we might want to reuse
the same socket for multiple requests to the same http server.


This is exactly the sort of issue I'm referring to.

a #:keep-alive? type keyword is the solution I'm suggesting, as it would
allow a hypothetical

(close-port
  (make-deflate-input-port
    (make-chunked-input-port socket #:close-underlying-port? #f)))

to perform the necessary cleanup for the transfer encoding ports, while
still keeping the original socket open for reuse. http-get doesn't need
to factor into this design decision at all, though the use of
#keep-alive? there does suggest that a solution like this may be
necessary.

Anyway, just talking about it out loud, seems to have convinced my that
this is "the right thing", though I'm not sure of the keyword
name. #:keep-alive? could work in a pinch, I guess.

Yours overthinkingly,

Re: Working http-get example and still unsolved problem

Sunjoong Lee — 2012-05-07T14:40:37

Hi, Ian;

2012/5/7 Ian Price <ianprice90< at >googlemail.com>


I don't understand the "close-port issue" exactly so this might be
nonsense. I think you mean comment-out-ed (close-port port) of close
in make-chunked-input-port.

http-get in client.scm calls close-port when keep-alive? keyword be false
value. http-post of Greg Benison's use keep-alive? keyword only when making
headers and does not call close-port; this is why my cc-ing to Greg.

In this today morning, I had thought what points need to patch if being
https support. I had no experience to making that kind of codes and can't
imagine I myself write it, so just a thought.

open-socket-for-uri need to make a session using gnu-tls; it does handshake
with a server and so on. http-get (and http-post) need to send bye to that
session when keep-alive? keyword be false value. So, close-port might be a
role of http-get?

Re: Working http-get example and still unsolved problem

Ian Price — 2012-05-07T05:16:19


Odd that I hadn't noticed this issue when I was testing. The problem
occurs in the case where the number to be read is less than the
remaining size of a chunk. I was updating the count with the buffer
size, rather than the difference, which leads to negative values on the
recursive call. There was also a mistake in the same case in updating
the buffer-pointer.

Thanks for pointing this out, and if you have other comments on the
implementation (and the close-port issue), I'll be happy to have them.

Re: Working http-get example and still unsolved problem

Sunjoong Lee — 2012-05-06T23:37:18

Ian had made a new patch for Chunked Encoding,
http://lists.gnu.org/archive/html/guile-devel/2012-05/msg00040.html ;
thanks Ian. But I suspect it has a bug.

make-chunked-input-port use bytevector-copy! in read!. I saw the crash like
this;
  ERROR: In procedure bytevector-copy!:
  ERROR: Value out of range 0 to 4294967295: -5915

I can't tell the url of the web page made that crash because I had seen it
in my testing login to that page but can tell you that was not written by
english and the charset of that is not UTF-8. I suspect the cause of the
crash be in using bytevector-copy!.

The previous patch made in 06 Nov 2011 does not make a crash. With that, I
could not read the content body of the page but it might be my fault.

2012/5/2 Sunjoong Lee <sunjoong< at >gmail.com>

http-read with cookie

Sunjoong Lee — 2012-05-06T07:39:27

Hello,

There is http-get in Guile and will be http-put, then what's the next? I
think the method using cookie and handling https. I had thought that I'd be
able to read contents of a web page needing login when I had read http-put
of Greg Benison,
http://lists.gnu.org/archive/html/guile-user/2012-04/msg00012.html .
How naive am I.

I recognize we need handling https because most login process of web pages
require it but have no idea of it now. During some trial, I made a very
little effort and want to share it. Of course, there shold be the better
way; I'm a newbie yet.

1.1 Exampe of http-get:

(receive (header body)
    (http-get (string->uri "http://code.google.com/"))
  (display header)
  (newline))
(receive (header body)
    (http-get (string->uri "http://code.google.com/"))
  (display header)
  (newline))

1.2 Output of above example:

#<<response> version: (1 . 1) code: 200 reason-phrase: "OK" headers: ((vary
accept-language cookie referer) (content-type text/html (charset .
"ISO-8859-1")) (etag "fe11bb5c119a4c282ecbc99fc66bc7f1" . #t)
(last-modified . #<date nanosecond: 0 second: 41 minute: 20 hour: 23 day: 5
month: 5 year: 2012 zone-offset: 0>) (date . #<date nanosecond: 0 second: 9
minute: 3 hour: 7 day: 6 month: 5 year: 2012 zone-offset: 0>) (expires .
#<date nanosecond: 0 second: 9 minute: 3 hour: 7 day: 6 month: 5 year: 2012
zone-offset: 0>) (cache-control private (max-age . 3600))
(x-content-type-options . "nosniff") (set-cookie .
"PREF=ID=6d783c184a55e937:TM=1336287789:LM=1336287789:S=p7v3fPvc55hTb15k;
expires=Tue, 06-May-2014 07:03:09 GMT; path=/; domain=.google.com") (server
. "codesite_static_content") (x-xss-protection . "1; mode=block")
(x-frame-options . "SAMEORIGIN") (connection close)) port: #<closed: file
0>>
#<<response> version: (1 . 1) code: 200 reason-phrase: "OK" headers: ((vary
accept-language cookie referer) (content-type text/html (charset .
"ISO-8859-1")) (etag "fe11bb5c119a4c282ecbc99fc66bc7f1" . #t)
(last-modified . #<date nanosecond: 0 second: 46 minute: 32 hour: 4 day: 6
month: 5 year: 2012 zone-offset: 0>) (date . #<date nanosecond: 0 second:
10 minute: 3 hour: 7 day: 6 month: 5 year: 2012 zone-offset: 0>) (expires .
#<date nanosecond: 0 second: 10 minute: 3 hour: 7 day: 6 month: 5 year:
2012 zone-offset: 0>) (cache-control private (max-age . 3600))
(x-content-type-options . "nosniff") (set-cookie .
"PREF=ID=e7e80585317f6678:TM=1336287790:LM=1336287790:S=PQWgTbaxsZyIqeVy;
expires=Tue, 06-May-2014 07:03:10 GMT; path=/; domain=.google.com") (server
. "codesite_static_content") (x-xss-protection . "1; mode=block")
(x-frame-options . "SAMEORIGIN") (connection close)) port: #<closed: file
0>>

1.3 Discussion about above output:
1) We need a web page using cookie. I picked http://code.google.com/ ; it
set PREF cookie once unlike http://www.google.com/ twice.
2) Example displays two headers, so the output is two line. In the first
line, http://code.google.com/ replied with set-cookie PREF. You may want to
send cookie header when the next request. If not so, the server would
re-send set-cookie PREF again as seen in second line.
3) Cookie header is essential when making a session. In above example, of
course, actually no need to making a session, so no need cookie, it's just
a test.

2.1 Example of http-read:

(receive (header body)
    (http-read "http://code.google.com/")
  (display header)
  (newline))
(receive (header body)
    (http-read "http://code.google.com/")
  (display header)
  (newline))

2.2 Output of above example:

#<<response> version: (1 . 1) code: 200 reason-phrase: "OK" headers: ((vary
accept-language cookie referer) (content-type text/html (charset .
"ISO-8859-1")) (etag "fe11bb5c119a4c282ecbc99fc66bc7f1" . #t)
(last-modified . #<date nanosecond: 0 second: 46 minute: 32 hour: 4 day: 6
month: 5 year: 2012 zone-offset: 0>) (date . #<date nanosecond: 0 second:
58 minute: 23 hour: 7 day: 6 month: 5 year: 2012 zone-offset: 0>) (expires
. #<date nanosecond: 0 second: 58 minute: 23 hour: 7 day: 6 month: 5 year:
2012 zone-offset: 0>) (cache-control private (max-age . 3600))
(x-content-type-options . "nosniff") (set-cookie .
"PREF=ID=8253d36f6bcd8b99:TM=1336289038:LM=1336289038:S=xDYcthWhrVAC2asa;
expires=Tue, 06-May-2014 07:23:58 GMT; path=/; domain=.google.com") (server
. "codesite_static_content") (x-xss-protection . "1; mode=block")
(x-frame-options . "SAMEORIGIN") (connection close)) port: #<closed: file
0>>
#<<response> version: (1 . 1) code: 200 reason-phrase: "OK" headers: ((vary
accept-language cookie referer) (content-type text/html (charset .
"ISO-8859-1")) (etag "fe11bb5c119a4c282ecbc99fc66bc7f1" . #t)
(last-modified . #<date nanosecond: 0 second: 46 minute: 32 hour: 4 day: 6
month: 5 year: 2012 zone-offset: 0>) (date . #<date nanosecond: 0 second:
58 minute: 23 hour: 7 day: 6 month: 5 year: 2012 zone-offset: 0>) (expires
. #<date nanosecond: 0 second: 58 minute: 23 hour: 8 day: 6 month: 5 year:
2012 zone-offset: 0>) (cache-control public (max-age . 3600))
(x-content-type-options . "nosniff") (server . "codesite_static_content")
(x-xss-protection . "1; mode=block") (x-frame-options . "SAMEORIGIN")
(connection close)) port: #<closed: file 0>>

2.3 Discussion about above output:

1) http-read can accept a string URL as it's first argument; of course, it
can accept a uri object like result of string->uri.
2) In the first line, the server replied with set-cookie PREF like 1.2 but
there is no second set-cookie PREF in the second line because http-read had
sent cookie header when second request.

I had attatched a code of http-read.

Re: Problem with guile on Dragora

Germán A. Arias — 2012-05-06T01:12:23

El Sat, 5 May 2012 04:46:45 +0900
Sunjoong Lee <sunjoong< at >gmail.com> escribió:

There no "FAIL" or "ERROR", just "WARNINGS". Attached the
check-guile.log.