GNU Guile 1.8.7 released

GNU Guile 1.8.7 released

[Ludovic Courtès]

[-- Attachment #1: Type: text/plain, Size: 4225 bytes --]

We are pleased to announce GNU Guile release 1.8.7.  This is the next
maintenance release for the 1.8 stable series.  It provides a number of
portability improvements, bug fixes, as well as several new features.

The Guile web page is located at http://gnu.org/software/guile/, and
among other things, it contains a link to the Guile FAQ and pointers to
the mailing lists.

Guile is an interpreter for the Scheme programming language, with
support for many SRFIs, packaged for use in a wide variety of
environments.  In addition to implementing the R5RS Scheme standard,
Guile includes a module system, full access to POSIX system calls,
networking support, multiple threads, dynamic linking, a foreign
function call interface, and powerful string processing.

Guile can run interactively or as a script interpreter, and is also
packaged as a library so that applications can easily incorporate a
complete Scheme interpreter.  An application can use Guile as an
extension language, a clean and powerful configuration language, or as
multi-purpose "glue" to connect primitives provided by the application.
It is easy to call Scheme code from C code and vice versa.  Applications
can add new functions, data types, control structures, and even syntax
to Guile, to create a domain-specific language tailored to the task at
hand.


Here are the compressed sources:
  ftp://ftp.gnu.org/gnu/guile/guile-1.8.7.tar.gz   (3.9MB)

Here are the GPG detached signatures[*]:
  ftp://ftp.gnu.org/gnu/guile/guile-1.8.7.tar.gz.sig

Here are the MD5 and SHA1 checksums:

991b5b3efcbbc3f7507d05bc42f80a5e  guile-1.8.7.tar.gz
24cd2f06439c76d41d982a7384fe8a0fe5313b54  guile-1.8.7.tar.gz

[*] You can use either of the above signature files to verify that
the corresponding file (without the .sig suffix) is intact.  First,
be sure to download both the .sig file and the corresponding tarball.
Then, run a command like this:

  gpg --verify guile-1.8.7.tar.gz.sig

If that command fails because you don't have the required public key,
then run this command to import it:

  gpg --keyserver keys.gnupg.net --recv-keys EA52ECF4

and rerun the `gpg --verify' command.

This release was bootstrapped with the following tools:
  Autoconf 2.63
  Automake 1.11
  Libtool 2.2.6


This is primarily a bugfix release.  Here are the highlights, taken from
the `NEWS' file:

  * Bugs fixed

  ** Fix compilation with `--disable-deprecated'
  ** Fix %fast-slot-ref/set!, to avoid possible segmentation fault
  ** Fix MinGW build problem caused by HAVE_STRUCT_TIMESPEC confusion
  ** Fix build problem when scm_t_timespec is different from struct timespec
  ** Fix build when compiled with -Wundef -Werror
  ** More build fixes for `alphaev56-dec-osf5.1b' (Tru64)
  ** Build fixes for `powerpc-ibm-aix5.3.0.0' (AIX 5.3)
  ** With GCC, always compile with `-mieee' on `alpha*' and `sh*'
  ** Better diagnose broken `(strftime "%z" ...)' in `time.test' (bug #24130)
  ** Fix parsing of SRFI-88/postfix keywords longer than 128 characters
  ** Fix reading of complex numbers where both parts are inexact decimals
  ** Allow @ macro to work with (ice-9 syncase)
  ** Have `scm_take_locale_symbol ()' return an interned symbol (bug #25865)
  ** Fix potential deadlocks when running on multiple threads
  ** Fix problems building with the i586-mingw32msvc cross-compiler


Any bugs found in this release will be addressed by further bugfix
releases numbered 1.8.*.

You can follow Guile development in the Git repository and on the Guile
mailing lists.  Guile builds from the `master' branch of Git have
version number 1.9.x and will eventually lead to the 2.0 stable series.

Guile versions with an odd middle number, e.g., 1.9.*, are unstable
development versions.  Even middle numbers indicate stable versions.
This has been the case since the 1.3.* series.

Please report bugs through the Savannah bug tracker:

  https://savannah.gnu.org/bugs/?group=guile

Alternatively, bug reports can be sent to `bug-guile@gnu.org'.  We also
welcome reports of successful builds, which can be sent to the same
email address.


Ludovic Courtès, on behalf of the Guile team.

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

popen test hangs (was GNU Guile 1.8.7 released)

[Marijn Schouten (hkBst)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ludovic � wrote:
> We are pleased to announce GNU Guile release 1.8.7.

Hi,

it seems that the popen test hangs:

;;; (foo-pws)
Running exceptions.test
Running filesys.test
Running format.test
Running fractions.test
Running ftw.test
Running gc.test
Running getopt-long.test
Running goops.test
Running guardians.test
Running hash.test
Running hooks.test
Running import.test
Running interp.test
Running list.test
Running load.test
Running modules.test
Running numbers.test
Running optargs.test
Running options.test
Running poe.test
Running popen.test

then it hangs for at least an hour or so. My configure invocation is:

./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu
- --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share
- --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64
- --disable-error-on-warning --disable-static --enable-posix --disable-networking
- --enable-regex --enable-deprecated --disable-elisp --enable-nls --disable-rpath
- --disable-debug-freelist --disable-debug-malloc --disable-guile-debug
- --with-threads --with-modules EMACS=no

Any ideas what could be wrong or how to find out more?

Marijn

- --
If you cannot read my mind, then listen to what I say.

Marijn Schouten (hkBst), Gentoo Lisp project, Gentoo ML
<http://www.gentoo.org/proj/en/lisp/>, #gentoo-{lisp,ml} on FreeNode
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkpR1LoACgkQp/VmCx0OL2y9FACgyQwm21xm2B40mnTi26ravgnl
rPgAoL9cnTKQ9vT6DGrxEZKcm7qqp56K
=m4+J
-----END PGP SIGNATURE-----

Re: popen test hangs

[Neil Jerram]

"Marijn Schouten (hkBst)" <hkBst@gentoo.org> writes:

> it seems that the popen test hangs:

Grrr.  I thought we'd nailed that...

> then it hangs for at least an hour or so. My configure invocation is:
>
> ./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu
> --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share
> --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64
> --disable-error-on-warning --disable-static --enable-posix --disable-networking
> --enable-regex --enable-deprecated --disable-elisp --enable-nls --disable-rpath
> --disable-debug-freelist --disable-debug-malloc --disable-guile-debug
> --with-threads --with-modules EMACS=no
>
> Any ideas what could be wrong or how to find out more?

Please look at the end of the check-guile.log file, to find out the
last test case that ran successfully, before the one that hung.

Then, if you like you could confirm that it is the next test that is
the problem, by removing everything all the other tests from
popen.test, and running just popen.test with

  ./pre-inst-guile -s test-suite/tests/popen.test

Then, if possible, add debugging (display ...) lines, use GDB, etc.,
to try to find out more about the hang.

Thanks!
        Neil

Re: popen test hangs

[Marijn Schouten (hkBst)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Neil Jerram wrote:
> "Marijn Schouten (hkBst)" <hkBst@gentoo.org> writes:
> 
>> it seems that the popen test hangs:
> 
> Grrr.  I thought we'd nailed that...
> 
>> then it hangs for at least an hour or so. My configure invocation is:
>>
>> ./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu
>> --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share
>> --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64
>> --disable-error-on-warning --disable-static --enable-posix --disable-networking
>> --enable-regex --enable-deprecated --disable-elisp --enable-nls --disable-rpath
>> --disable-debug-freelist --disable-debug-malloc --disable-guile-debug
>> --with-threads --with-modules EMACS=no
>>
>> Any ideas what could be wrong or how to find out more?
> 
> Please look at the end of the check-guile.log file, to find out the
> last test case that ran successfully, before the one that hung.

check-guile.log ends with

PASS: popen.test: open-input-pipe: no args
PASS: popen.test: open-input-pipe: port?
PASS: popen.test: open-input-pipe: echo hello
PASS: popen.test: open-input-pipe: stdin==stderr
PASS: popen.test: open-input-pipe: stdout==stderr
PASS: popen.test: open-input-pipe: open-input-pipe process gets
(current-input-port) as stdin
PASS: popen.test: open-input-pipe: no duplicate
PASS: popen.test: open-output-pipe: no args
PASS: popen.test: open-output-pipe: port?
PASS: popen.test: open-output-pipe: stdin==stderr
PASS: popen.test: open-output-pipe: stdout==stderr

> Then, if you like you could confirm that it is the next test that is
> the problem, by removing everything all the other tests from
> popen.test, and running just popen.test with
> 
>   ./pre-inst-guile -s test-suite/tests/popen.test
> 
> Then, if possible, add debugging (display ...) lines, use GDB, etc.,
> to try to find out more about the hang.
> 
> Thanks!
>         Neil


- --
If you cannot read my mind, then listen to what I say.

Marijn Schouten (hkBst), Gentoo Lisp project, Gentoo ML
<http://www.gentoo.org/proj/en/lisp/>, #gentoo-{lisp,ml} on FreeNode
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkpSj8UACgkQp/VmCx0OL2xLWACfbCptX75eveVg5A3Hf5d49sp/
W9sAmQGrkBh5ytzzL4jbLXVmZEWml97U
=VaKC
-----END PGP SIGNATURE-----

Re: popen test hangs

[Marijn Schouten (hkBst)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Marijn Schouten (hkBst) wrote:
> Neil Jerram wrote:
>> "Marijn Schouten (hkBst)" <hkBst@gentoo.org> writes:
> 
>>> it seems that the popen test hangs:
>> Grrr.  I thought we'd nailed that...
> 
>>> then it hangs for at least an hour or so. My configure invocation is:
>>>
>>> ./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu
>>> --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share
>>> --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64
>>> --disable-error-on-warning --disable-static --enable-posix --disable-networking
>>> --enable-regex --enable-deprecated --disable-elisp --enable-nls --disable-rpath
>>> --disable-debug-freelist --disable-debug-malloc --disable-guile-debug
>>> --with-threads --with-modules EMACS=no
>>>
>>> Any ideas what could be wrong or how to find out more?
>> Please look at the end of the check-guile.log file, to find out the
>> last test case that ran successfully, before the one that hung.
> 
> check-guile.log ends with
> 
> PASS: popen.test: open-input-pipe: no args
> PASS: popen.test: open-input-pipe: port?
> PASS: popen.test: open-input-pipe: echo hello
> PASS: popen.test: open-input-pipe: stdin==stderr
> PASS: popen.test: open-input-pipe: stdout==stderr
> PASS: popen.test: open-input-pipe: open-input-pipe process gets
> (current-input-port) as stdin
> PASS: popen.test: open-input-pipe: no duplicate
> PASS: popen.test: open-output-pipe: no args
> PASS: popen.test: open-output-pipe: port?
> PASS: popen.test: open-output-pipe: stdin==stderr
> PASS: popen.test: open-output-pipe: stdout==stderr
> 
>> Then, if you like you could confirm that it is the next test that is
>> the problem, by removing everything all the other tests from
>> popen.test, and running just popen.test with
> 
>>   ./pre-inst-guile -s test-suite/tests/popen.test

Actually doing this allowed the tests to run perfectly. That makes it look like
it is some interaction between popen.test and the sandbox/package manager. I
will investigate further.

Thanks,

Marijn

- --
If you cannot read my mind, then listen to what I say.

Marijn Schouten (hkBst), Gentoo Lisp project, Gentoo ML
<http://www.gentoo.org/proj/en/lisp/>, #gentoo-{lisp,ml} on FreeNode
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkpTWcUACgkQp/VmCx0OL2yU0ACfeixckXA2zRbFX1ROAFvZ3xK9
0pAAoIWcDQvOMQPu+vuLxXnlrHvIjpds
=1wvz
-----END PGP SIGNATURE-----

Re: popen test hangs

[Neil Jerram]

"Marijn Schouten (hkBst)" <hkBst@gentoo.org> writes:

>> check-guile.log ends with
>> 
>> PASS: popen.test: open-input-pipe: no args
>> PASS: popen.test: open-input-pipe: port?
>> PASS: popen.test: open-input-pipe: echo hello
>> PASS: popen.test: open-input-pipe: stdin==stderr
>> PASS: popen.test: open-input-pipe: stdout==stderr
>> PASS: popen.test: open-input-pipe: open-input-pipe process gets
>> (current-input-port) as stdin
>> PASS: popen.test: open-input-pipe: no duplicate
>> PASS: popen.test: open-output-pipe: no args
>> PASS: popen.test: open-output-pipe: port?
>> PASS: popen.test: open-output-pipe: stdin==stderr
>> PASS: popen.test: open-output-pipe: stdout==stderr

Thanks, that indicates this test:

  (pass-if "open-input-pipe process gets (current-input-port) as stdin"
    (let* ((p2c (pipe))
           (port (with-input-from-port (car p2c)
                   (lambda ()
                     (open-input-pipe "read line && echo $line")))))
      (display "hello\n" (cdr p2c))
      (force-output (cdr p2c))
      (let ((result (eq? (read port) 'hello)))
	(close-port (cdr p2c))
	(close-pipe port)
	result)))

We had trouble with this one because of different shells.  The
open-input-pipe line was originally "read && echo $REPLY", but that
didn't work in Dash, so we changed it to "read line && echo $line" as
shown above.

Is it possible that your sandbox/package manager uses a different
shell from what is used when you run

>>>   ./pre-inst-guile -s test-suite/tests/popen.test

by hand, and that "read line && echo $line" doesn't work in the
sandbox/package manager shell?

Thanks,
        Neil