bug#14421: Unable to build Guile 2.0.9

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

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:

> GET / HTTP/1.1
> Host: example.com
> Authorization: basic dXNlcm5hbWU6cGFzc3dvcmQ=

Actual output:

> GET / HTTP/1.1
> Host: example.com
> Authorization: basic

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.

-- Atom X Zane

* module/web/http.scm: modify write-credentials to display the
  base64-encoded concatenation of username and password if the
  authorization model is 'basic
---
 module/web/http.scm |    6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/module/web/http.scm b/module/web/http.scm
index 35169ef..0e5db5d 100644
--- a/module/web/http.scm
+++ b/module/web/http.scm
 <at>  <at>  -913,10 +913,10  <at>  <at>  as an ordered alist."

 (define (write-credentials val port)
   (display (car val) port)
+  (display #\space port)
   (if (pair? (cdr val))
-      (begin
-        (display #\space port)
-        (write-key-value-list (cdr val) port))))
+      (write-key-value-list (cdr val) port)
+      (display (cdr val) port)))

 ;; challenges = 1#challenge
 ;; challenge = auth-scheme 1*SP 1#auth-param
--

-- 
1.7.10.4

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

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

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> (guile-user)> (define k (reset (shift k k) (values 3.1 2 3)))
scheme <at> (guile-user)> (k)
$8 = 3.1
scheme <at> (guile-user)> (k)
$9 = 3.1

(I installed guile-2.0 with apt-get on Ubuntu and got this.)

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

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
--

-- 
Cyprien/Fulax

http://www.gnu.org/software/guile/developers.html

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

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
--

-- 
Cyprien/Fulax

bug#14219: ./configure

bug#14203: Manual: 'my-or'; 'let' inside macros

I think this example [1,2]:

(define-syntax my-or
  (syntax-rules ()
    ((my-or)
     #t)
    ((my-or exp)
     exp)
    ((my-or exp rest ...)
     (let ((t exp))
       (if exp
           exp
           (my-or rest ...))))))

should look like this:

(define-syntax my-or
  (syntax-rules ()
    ((my-or)
     #t)
    ((my-or exp)
     exp)
    ((my-or exp rest ...)
     (let ((t exp))
       (if t                    ; <-
           t
           (my-or rest ...))))))

Otherwise, what's the rationale behind 'let'?

AFAICT, it's described here [3], but Guile is not affected, right?  So
the following works as well:

(define-syntax my-or
  (syntax-rules ()
    ((my-or)
     #t)
    ((my-or exp)
     exp)
    ((my-or exp rest ...)
     (if exp
         exp
         (my-or rest ...)))))

Note that 'my-or' is used in several places (e.g., [4]) and it's
necessary to change them all.  Also, there are other macros that use
'let' (e.g., 'cond1').

[1] https://gnu.org/software/guile/manual/guile.html#Defining-Macros
[2] https://gnu.org/software/guile/manual/guile.html#Hygiene
[3] http://stackoverflow.com/a/3215238
[4] https://gnu.org/software/guile/manual/guile.html#Syntax-Case

bug#14201: guile build issue under Mac OS X

Hi there,

I just tried building guile 2.0.9 under three versions of Mac OS X (10.6.8, 10.7.5 and 10.8.3). In all cases I
get the following error:

<snip>
Making all in lib
make[2]: Entering directory `/private/tmp/guile-2.0.9/lib'
make[2]: ../build-aux/install-sh: Command not found
make[2]: *** [arpa/inet.h] Error 127
make[2]: Leaving directory `/private/tmp/guile-2.0.9/lib'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/private/tmp/guile-2.0.9'
make: *** [all] Error 2
</snip>

Notes:
* the tile /private/tmp/guile-2.0.9/build-aux/install-sh does exist and is executable.
* /usr/include/arpa/inet.h is also available, so no CPPFLAGS should be needed

Any ideas?

--
Marius Schamschula

bug#14193: Build system: touching ports.h fails to rebuild sockets.o and posix.o

Touching ports.h fails to rebuild sockets.o and posix.o.  Both sockets.c
and posix.c include fports.h, which includes ports.h, so this rebuild
should be automatic.

Andy pointed out that this probably has to do with the special handling
of sockets.c and posix.c:

* Both are conditionally included depending on configuration.

* Their object files don't include "libguile_2.0_la" in the names.

     Mark