gmane.lisp.guile.bugs

bug#14421: Unable to build Guile 2.0.9

Andy Wingo — 2013-05-21T19:51:01

Hi,

Please keep the bug in the Cc.  Thanks.

On Tue 21 May 2013 17:35, Douglas Mencken <dougmencken< at >gmail.com> writes:


reclaim.c is in libgc.  This means you have a broken libgc installation.

Andy

bug#14421: Unable to build Guile 2.0.9

Andy Wingo — 2013-05-20T18:44:47

Hi Douglas,

On Sat 18 May 2013 23:05, Douglas Mencken <dougmencken< at >gmail.com> writes:


What platform is this on?  Have you successfully compiled Guile in the
past?

What is your locale?  If you try with LC_ALL=C does it work?

I wonder if this is related somehow with the gnulib regexp update we did
recently.

Andy

bug#14404: regexp_exec thread-unsafe

Ludovic Courtès — 2013-05-20T14:20:08

Paul Eggert <eggert< at >cs.ucla.edu> skribis:


Thank you for the quick reply.  I haven’t tested yet, but I have a question:


Seems like this is going to add -lpthread to LDFLAGS, right?

That would raise two issues: first, it should add -pthread to both
CFLAGS and LDFLAGS, not just -lpthread.

Second, Guile can be compiled with and without thread support.  In the
latter case, we wouldn’t want Gnulib to stealthily pull in pthreads.
How can this be addressed?

Thanks!

Ludo’.

bug#14421: Unable to build Guile 2.0.9

Douglas Mencken — 2013-05-18T21:05:38

I'm trying to build Guile release 2.0.9, but it prints errors instead of
successful build:
http://manulix.wikidot.com/issues#toc3

  SNARF  regex-posix.doc
  GEN      guile-procedures.texi
Backtrace:
In unknown file:
   ?: 12 [apply-smob/1 #<boot-closure 108966c0 (_ _ _)> #t ...]
   ?: 11 [apply-smob/1 #<catch-closure 10942570>]
   ?: 10 [primitive-eval ((< at > # %) (begin # # #))]
   ?: 9 [primitive-load "/root/build-farm/guile-v2.0.9.builddir/meta/guild"]
   ?: 8 [primitive-eval (define-module (guild) #:use-module ...)]
   ?: 7 [apply-smob/1 #<boot-closure 10998ce0 (_)> (define-module # # # ...)]
   ?: 6 [apply-smob/1 #<boot-closure 10acea10 ()>]
   ?: 5 [apply-smob/1 #<boot-closure 10ace9f0 ()>]
   ?: 4 [apply-smob/1 #<boot-closure 10ad1c70 ()>]
   ?: 3 [primitive-eval #<struct:1080ac78 pwpwpwpwpw 10949b20>]
   ?: 2 [primitive-load-path "ice-9/getopt-long" #<boot-closure 1081e430 ()>]
   ?: 1 [primitive-eval (define short-opt-rx (make-regexp "^-([a-zA-Z]+)(.*)"))]
   ?: 0 [make-regexp "^-([a-zA-Z]+)(.*)"]

ER

bug#14404: regexp_exec thread-unsafe

Ludovic Courtès — 2013-05-15T07:34:03

And here’s a reduced test case that “works” quite well on Guile 2.0.9:

--8<---------------cut here---------------start------------->8---
(use-modules (ice-9 threads)
             (ice-9 regex)
             (web uri)
             (srfi srfi-1)
             (srfi srfi-26))

(let ((do-regexps (lambda ()
                    (define seed1 (random 100000))
                    (define seed2 (random 100000))
                    (let loop ()
                      (let ((p (make-regexp "^http://([^/]+)/(.*)$"))
                            (s (string-append
                                "http://" (number->string seed1)
                                "hydra.gnu.org/nar/0did57blsaaspj49cl3q8nnydm5pr1qg-cflow-1.4"
                                (number->string seed2))))
                        (or (uri? (string->uri s))
                            (exit 42))
                        (regexp-exec p s)
                        (loop))))))
  (unfold (cute >= <> (current-processor-count))
          (lambda (i)

bug#14370: [PATCH] Write out HTTP Basic auth headers correctly

Atom X Zane — 2013-05-08T08:50:15

HTTP Basic authorization headers are not output correctly, leaving off
the user credentials in the Authorization: header.

Test case:

(let ((req (build-request
            (build-uri
             'http
             #:host "example.com")
            #:headers '((authorization
                         basic . "dXNlcm5hbWU6cGFzc3dvcmQ=")
                                      ))))
  (write-request req (current-output-port)))

Expected output:


Actual output:



As you can see, the user credentials aren't actually written out,
causing the server to return a "401 Authorization required" response.  I
have included a patch which remedies this problem.

bug#14361: Building guile 2.0.9 under mingw + msys

Eli Zaretskii — 2013-05-07T17:18:05

Thanks, and sorry for a long delay.

I tried today building Guile 2.0.9.  The C compilation went very
smoothly, with only a couple of warnings (one is the known iconv
prototype "issue", the other a variable that is set and not used).
However, once it got to compiling Scheme files, it repeatedly failed
after writing each .go file.  Here are a few typical failures:

       GEN      guile-procedures.texi
     Backtrace:
     In unknown file:
?: 3 [apply-smob/1 #<boot-closure 234da60 (_ _ _)> #t ...]
?: 2 [apply-smob/1 #<catch-closure 2e07050> quit #<unspecified>]
?: 1 [apply-smob/1 #<boot-closure 234da60 (_ _ _)> #t ...]
?: 0 [apply-smob/1 #<catch-closure 3f7eea0>]

     ERROR:

The program then sits at the ERROR: prompt, but does not accept any
input.

Seems that this comes from smob.c:

     static SCM
     scm_smob_trampoline (unsigned int nreq, unsigned int nopt,
  unsigned int rest)
     {
       SCM trampoline;

       if (SCM_UNLIKELY (rest > 1 || nreq + nopt + rest > 3))
 scm_out_of_range ("mak

bug#14347: reset, shift, continuation values truncated inconsistently

Stefan Israelsson Tampe — 2013-05-06T21:15:13

Hmm, we have

(let ((k (cal-with-prompt tag (-- expr that ends with (values a b c) --)
 (-- expr that is of unknown values length --))))
  (k))

So it looks like peval.scm in language/tree-il does not handle this well.

Looking in that file we have

(($ <prompt> src tag body handler)
       (define (make-prompt-tag? x)
         (match x
           (($ <application> _ ($ <primitive-ref> _ 'make-prompt-tag)
               (or () ((? constant-expression?))))
            #t)
           (_ #f)))

       (let ((tag  (for-value tag))
             (body (for-tail body)))

       ... cases where we can optimize sue to knowledge of prompt-tag ...

       (else
           (make-prompt src tag body (for-value handler))))))

So to me it looks like peval does a for-tail on body, and uses the value
constraint on the body. I'm not sure how to fix this though.

But that this is the problem can be shown by changing the code to

(($ <prompt> src tag body-in handler)
       (define (make-prompt-tag? x)
         (match x

bug#14347: reset, shift, continuation values truncated inconsistently

Ian Price — 2013-05-06T19:06:30

Totally agree, this is the behaviour I expect


scheme< at >(guile−user)> (import (only (rnrs) let-values))
scheme< at >(guile−user)> (let ((k (reset (shift k k) (values 3.1 2 3)))) (k))
$40 = 3.1
scheme< at >(guile−user)> (let-values (((k) (reset (shift k k) (values 3.1 2 3)))) (k))
$41 = 3.1
$42 = 2
$43 = 3

So, my first suspicion was that there is some part of the code that
receives the multiple values in a let or something, but neither the
code, nor the ,expand command revealed that. However, when we check with
,optimize

(let ((k (call-with-prompt
           ((< at >< at > (ice-9 control) default-prompt-tag))
           (lambda ()
             (apply abort
                    ((< at >< at > (ice-9 control) default-prompt-tag))
                    (lambda (cont)
                      (call-with-prompt
                        ((< at >< at > (ice-9 control) default-prompt-tag))
                        (lambda ()
                          (lambda vals
                            (call-with-prompt
                              ((< at >< at > (ice-9 contro

bug#14353: Implement array-fold and array-fold-all

Jez — 2013-05-06T03:32:26

Right now there are no library functions for folding over arrays (or
bytevectors, etc.) This implements them. fold-all produces a single value
regardless of the number of dimensions of the array; it is implemented on
top of array-for-each. array-fold produces an array of rank n-1, where n is
the rank of the original array.

I'll write up documentation if the code looks acceptable.

Regards,
Jez

bug#14354: Implement array-fold and array-fold-all

Jez — 2013-05-06T05:36:24

Ah, I reread my code and realized that I could compare array-types using
eq? instead of equals?. I'll change that once I get feedback on the current
patch.

Jez


On Mon, May 6, 2013 at 1:23 AM, Jez <jezreel< at >gmail.com> wrote:

bug#14354: Implement array-fold and array-fold-all

Jez — 2013-05-06T05:23:46

Right now there are no library functions for folding over arrays (or
bytevectors, etc.) This implements them. fold-all produces a single value
regardless of the number of dimensions of the array; it is implemented on
top of array-for-each. array-fold produces an array of rank n-1, where n is
the rank of the original array.

I'll write up documentation if the code looks acceptable.

Regards,
Jez

bug#14347: reset, shift, continuation values truncated inconsistently

Jussi Piitulainen — 2013-05-04T07:47:15

Hi, the following seems at least inconsistent to
me and possibly unintended: I believe it
demonstrates that the continuation captured by
`shift' passes all its values to its continuation
when it's called directly, but truncates them to
the first value when it's bound to a variable
outside the reset expression and then called.

The documentation for reset and shift in the
manual does not quite say, but I believe the
captured continuation in these examples should be
the continuation of the shift expression inside
the reset expression, that is, it should simply
return the three values in all cases.

GNU Guile 2.0.5-deb+1-3
Copyright (C) 1995-2012 Free Software Foundation, Inc.
...
Enter `,help' for help.
scheme< at >(guile-user)> (use-modules (ice-9 control))
scheme< at >(guile-user)> (reset (shift k (k)) (values 3.1 2 3))
$1 = 3.1
$2 = 2
$3 = 3
scheme< at >(guile-user)> ((reset (shift k k) (values 3.1 2 3)))
$4 = 3.1
$5 = 2
$6 = 3
scheme< at >(guile-user)> (let ((k (reset (shift k k) (values 3.1 2 3)))) (k))
$7 = 3.1
scheme< at >(guil

bug#14261: [guile-1.8] guile-readline fails to build withautomake-1.13

Cyprien Nicolas — 2013-04-24T23:18:19

Per Gentoo bug 467064 [1], aclocal.out reports:

----8<----8<----8<----8<----8<----8<----8<----8<-----

***** aclocal *****
***** PWD: /var/tmp/paludis/dev-scheme-guile-1.8.8-r1/work/guile-1.8.8/guile-readline
***** aclocal

aclocal-1.13: warning: autoconf input should be named 'configure.ac', not 'configure.in'
configure.in:12: error: 'AM_CONFIG_HEADER': this macro is obsolete.
    You should use the 'AC_CONFIG_HEADERS' macro instead.
/usr/share/aclocal-1.13/obsolete-err.m4:12: AM_CONFIG_HEADER is expanded from...
configure.in:12: the top level
autom4te-2.69: /usr/bin/m4 failed with exit status: 1
aclocal-1.13: error: echo failed with exit status: 1

---->8---->8---->8---->8---->8---->8---->8---->8----

I attach two patches here. The first one replace AM_CONFIG_HEADER with
AC_CONFIG_HEADERS and remove AM_PROG_CC_STDC from configure.in, while
se second one renames configure.in into configure.ac per above
warning.


1. https://bugs.gentoo.org/show_bug.cgi?id=467064

bug#14235: Grammar error onhttp://www.gnu.org/software/guile/developers.html

maxwell hansen — 2013-04-20T22:27:54

In the second sentence of the second paragraph it says "There is nothing
and stopping you from joining the team."

This is probably meant to say "There is nothing stopping you from joining
the team."

bug#14230: [Patch] guile-1.8, Fix texinfo files for makeinfo-5

Cyprien Nicolas — 2013-04-18T21:59:51

Hi here,

At Gentoo, we start shipping makeinfo-5, which makes the guile-1.8.8 
build fail. I wrote a patch that fixes the errors and warnings.

It does not break texinfo files for texinfo-4.13.

Cheers

bug#14219: ./configure

Mark H Weaver — 2013-04-17T19:21:54


Can you send us the "config.log" file?  Please keep
"14219< at >debbugs.gnu.org" in the CC line.

Out of curiosity, what language is your real name written in?  My email
client (Gnus v5.13 on Emacs 24.3) is unable to decode it properly.

      Mark

bug#14042: configure error for guile 2.0.7

Ludovic Courtès — 2013-04-15T16:07:49

Hi Marc,

Did ‘make check’ in libgc pass?

As for Guile, can you try configuring and building it with
--without-threads for a start, and report back?

Thanks,
Ludo’.

bug#14042: configure error for guile 2.0.7

Ludovic Courtès — 2013-04-15T16:06:15

Marc Girod <marc.girod< at >gmail.com> skribis:


Typo.

Ludo’.

bug#14171: Aw: Re: bug#14171: REPL doesn't work on windows min-gw

Jan Schukat — 2013-04-15T06:37:58

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 vari

bug#14201: guile build issue under Mac OS X

Ludovic Courtès — 2013-04-14T22:11:24

ludo< at >gnu.org (Ludovic Courtès) skribis:


For the record, the problem is that the scripts installed by
‘automake -a’, with Automake from Guix, would contain “patched” shebangs
referring to files under /nix/store:

  http://lists.gnu.org/archive/html/bug-guix/2013-04/msg00076.html

This is a serious issue that I’ve fixed now.

The Guile 2.0.9 tarball has several scripts in build-aux/ with invalid
shebangs.  “Fortunately”, apart from ‘install-sh’, they are normally
invoked as “$SHELL ./the-file”, so the shebang isn’t actually used.

Please accept my apologies...

Ludo’.