GNU Guile 1.8.4 released

GNU Guile 1.8.4 released

[Ludovic Courtès]

We are pleased to announce GNU Guile release 1.8.4.  This is the next
maintenance release for the 1.8 stable series.

You can find it here:

  ftp://ftp.gnu.org/gnu/guile/guile-1.8.4.tar.gz
  SHA1 hash: 1e80fe242acfde2bfa39fd1e8409a8f010e24e2b

A GPG detached signature of the package is available at:

  ftp://ftp.gnu.org/gnu/guile/guile-1.8.4.tar.gz.sig

The Guile web page is located at http://www.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.

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

  - Bugs fixed

   - CR (ASCII 0x0d) is (again) recognized as a token delimiter by the
     reader
   - Fixed a segmentation fault which occurred when displaying the
     backtrace of a stack with a promise object (made by `delay') in it
   - Make `accept' leave guile mode while blocking
   - `scm_c_read ()' and `scm_c_write ()' now type-check their port
     argument
   - Fixed a build problem on AIX (use of func_data identifier)
   - Fixed a segmentation fault which occurred when hashx-ref or
     hashx-set! was called with an associator proc that returns neither
     a pair nor #f.
   - Secondary threads now always return a valid module for
     (current-module).
   - Avoid MacOS build problems caused by incorrect combination of "64"
     system and library calls.
   - `guile-snarf' now honors `$TMPDIR'
   - `guile-config compile' now reports CPPFLAGS used at compile-time
   - Fixed build with Sun Studio (Solaris 9)
   - Fixed wrong-type-arg errors when creating zero length SRFI-4
     uniform vectors on AIX.
   - Fixed a deadlock that occurs upon GC with multiple threads.
   - Fixed compile problem with GCC on Solaris and AIX (use of _Complex_I)
   - Fixed autotool-derived build problems on AIX 6.1.
   - Fixed NetBSD/alpha support
   - Fixed MacOS build problem caused by use of rl_get_keymap(_name)

  - New modules (see the manual for details)

   - `(srfi srfi-69)'

  - Documentation fixes and improvements

   - Removed premature breakpoint documentation
   - More about Guile's default *random-state* variable
   - GOOPS: more about how to use `next-method'

  - Changes to the distribution

   - Corrected a few files that referred incorrectly to the old GPL +
     special exception licence
   - Removed unnecessary extra copies of COPYING*


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

You can follow Guile development in CVS and on the Guile mailing lists
(see ANON-CVS and HACKING).  Guile builds from the development branch
of CVS will have version number 1.9.0.

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 send bug reports to `bug-guile@gnu.org'.


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

Re: GNU Guile 1.8.4 released

[Kamaraju S Kusumanchi]

Ludovic Courtès wrote:

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

Just wanted to bring to your attention that guile 1.8.4 failed to build on
alpha, ia64 architectures. The build log can be found at

http://buildd.debian.org/fetch.cgi?pkg=guile-1.8&arch=alpha&ver=1.8.4%2B1-1&stamp=1203917145&file=log&as=raw

http://buildd.debian.org/fetch.cgi?pkg=guile-1.8&arch=ia64&ver=1.8.4%2B1-1&stamp=1203835823&file=log&as=raw

It would be great if they can be fixed.


raju
-- 
Kamaraju S Kusumanchi
http://www.people.cornell.edu/pages/kk288/
http://malayamaarutham.blogspot.com/

Re: GNU Guile 1.8.4 released

[Neil Jerram]

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

2008/5/15 Kamaraju Kusumanchi <kamaraju@bluebottle.com>:

> Not sure if you have  noticed already. The build has failed on ia64 with a
> segmentation fault. Here is the relevant log for ia64
>
>
> http://buildd.debian.org/fetch.cgi?pkg=guile-1.8&arch=ia64&ver=1.8.5%2B1-1&stamp=1210454760&file=log&as=raw


OK, now I'm confused.  I looked at the build log for ia64 from here -
http://buildd.debian.org/pkg.cgi?pkg=guile-1.8 - just a few minutes ago,
when responding to another FTBFS report, and I'm sure it said that it was
failing with an Illegal instruction in test-unwind.  Is there any reason why
these logs might be changing while I'm looking at them, or am I just going
mad?

On another matter...  it looks to me as though the build on alpha is now
good, so I guess we must somehow have fixed the cause of the "wrong type to
apply (#0# . #0#)" problem between 1.8.4 and 1.8.5.  Would you agree with
that, or am I misunderstanding the status?

Thanks,
      Neil

[-- Attachment #2: Type: text/html, Size: 1645 bytes --]

Re: GNU Guile 1.8.4 released

[Kamaraju Kusumanchi]

On Saturday 24 May 2008 5:19 pm, Neil Jerram wrote:
> 2008/5/15 Kamaraju Kusumanchi <kamaraju@bluebottle.com>:
> > Not sure if you have  noticed already. The build has failed on ia64 with
> > a segmentation fault. Here is the relevant log for ia64
> >
> >
> > http://buildd.debian.org/fetch.cgi?pkg=guile-1.8&arch=ia64&ver=1.8.5%2B1-
> >1&stamp=1210454760&file=log&as=raw
>
> OK, now I'm confused.  I looked at the build log for ia64 from here -
> http://buildd.debian.org/pkg.cgi?pkg=guile-1.8 - just a few minutes ago,
> when responding to another FTBFS report, and I'm sure it said that it was
> failing with an Illegal instruction in test-unwind.  Is there any reason
> why these logs might be changing while I'm looking at them, or am I just
> going mad?

Sometimes the buildd daemons attempt a rebuild for the failed packages. In 
this case this might be the reason you are seeing different errors at 
different times. May be they fixed something in the toolchain of ia64 
architecture.

Anyway, the correct (and easiest way IMHO) is to go to 

http://buildd.debian.org/~jeroen/status/

then enter 'guile-1.8' in the box. This leads to

http://buildd.debian.org/~jeroen/status/package.php?p=guile-1.8&suite=unstable

This page gives a nice summary of which builds have succeded and which builds 
have failed. From the above page I see that the guile 1.8.5 failed to build 
on ia64, m68k, mips, mipsel, powerpc. There have been 1 attempt for each of 
the architecture, except for ia64 where there have been 3 attempts to build 
the guile 1.8.5 package.

We do not need to worry about hurd-i386 as it seems to be lagging behind all 
the times. However getting guile build on all other architectures would be 
nice.

> am I misunderstanding the status?

My only suggestion (from personal experience) for this kind of build problems 
is to use 
http://buildd.debian.org/~jeroen/status/ and not http://buildd.debian.org/ . 
The presentation of results from Jeroen's page is much easier to understand 
than from http://buildd.debian.org/ .

hth
raju
-- 
Kamaraju S Kusumanchi
http://www.people.cornell.edu/pages/kk288/
http://malayamaarutham.blogspot.com/

----------------------------------------------------------------------
Finally - A spam blocker that actually works.
http://www.bluebottle.com/tag/4

Re: GNU Guile 1.8.4 released

[Ludovic Courtès]

Hello,

Kamaraju Kusumanchi <kamaraju@bluebottle.com> writes:

> http://buildd.debian.org/~jeroen/status/package.php?p=guile-1.8&suite=unstable
>
> This page gives a nice summary of which builds have succeded and which builds 
> have failed. From the above page I see that the guile 1.8.5 failed to build 
> on ia64, m68k, mips, mipsel, powerpc. There have been 1 attempt for each of 
> the architecture, except for ia64 where there have been 3 attempts to build 
> the guile 1.8.5 package.

The failure on PowerPC (at least) is clearly a regression in 1.8.5.  I
used to have access to a GNU/Linux PPC box but unfortunately, I no
longer do.

Can someone please help us fix this?  Viewing the backtrace at
segfault-time might already give hints.  An account on such a machine
would be even better.  :-)

Thanks,
Ludovic.

Re: GNU Guile 1.8.4 released

[Neil Jerram]

2008/5/29 Ludovic Courtès <ludo@gnu.org>:
> Hello,
>
> Kamaraju Kusumanchi <kamaraju@bluebottle.com> writes:
>
>> http://buildd.debian.org/~jeroen/status/package.php?p=guile-1.8&suite=unstable
>>
>> This page gives a nice summary of which builds have succeded and which builds
>> have failed. From the above page I see that the guile 1.8.5 failed to build
>> on ia64, m68k, mips, mipsel, powerpc. There have been 1 attempt for each of
>> the architecture, except for ia64 where there have been 3 attempts to build
>> the guile 1.8.5 package.
>
> The failure on PowerPC (at least) is clearly a regression in 1.8.5.  I
> used to have access to a GNU/Linux PPC box but unfortunately, I no
> longer do.
>
> Can someone please help us fix this?  Viewing the backtrace at
> segfault-time might already give hints.  An account on such a machine
> would be even better.  :-)

See Debian bug #481378.  The symptom on powerpc is the same as on mips
and ia64, so it's probably the same cause for all of them, and we
believe that cause is a mistake in the stack direction detection.

On the other hand, it doesn't quite make sense at the moment, so we
could be wrong!

     Neil

Re: GNU Guile 1.8.4 released

[Ludovic Courtès]

Hi,

"Neil Jerram" <neiljerram@googlemail.com> writes:

> See Debian bug #481378.  The symptom on powerpc is the same as on mips
> and ia64, so it's probably the same cause for all of them, and we
> believe that cause is a mistake in the stack direction detection.

OK, I thought these were different things.

> On the other hand, it doesn't quite make sense at the moment, so we
> could be wrong!

That sounds suspicious given that the detection code hasn't change for
ages (since 2003 according to `git-blame').

Thanks,
Ludovic.