Re: [Chicken-users] [ANN] CHICKEN 4.11.0 release candidate 2 available

[Matt Welland]

Operating system: Ubuntu 14.04
Hardware platform: x86-64
C Compiler: GCC 4.8.4
Installation works?: yes
Tests work?: Did not run tests
Installation of eggs works?: yes

The testsuite for my pet project, Megatest, passes with Chicken 4.11rc2. I did see the IUP based dashboard die with an assertion but I lost the message and it has been running fine after a clean recompile without -debug-info. I did compile with -debug-info and used feathers to step through some code successfully. It is possible that I had a mix of .o files, some with -debug-info and some without and possibly that caused the assertion (just speculating).

The following eggs are referenced in the source. Quite a few, but not all, are exercised in the testsuite:

apropos
base64
call-with-environment-variables
canvas-draw
csv
csv-xml
defstruct
directory-utils
dot-locking
fmt
format
hostinfo
http-client
intarweb
iup
json
md5
message-digest
nanomsg
numbers
pathname-expand
posix
posix-extras
postgresql
readline
regex
regex-case
rpc
s11n
sparse-vectors
spiffy
spiffy-directory-listing
spiffy-request-vars
sql-de-lite
sqlite3
srfi-1
srfi-13
srfi-18
srfi-19
srfi-69
ssax
sxml-modifications
sxml-serializer
tcp
test
trace
uri-common
z3
zmq

All in all, I'm ready to switch to 4.11. Thanks and kudos to the Chicken team.

The eggs I installed (using this Makefile http://www.kiatoa.com/cgi-bin/fossils/megatest/raw/utils/Makefile.installall?name=981091d91cd74d3815d832187d4e08172849d70c):

matchable readline apropos base64 regex-literals format regex-case test coops trace csv \
     dot-locking posix-utils posix-extras directory-utils hostinfo tcp-server rpc csv-xml fmt \
     json md5 awful http-client spiffy uri-common intarweb spiffy-request-vars pathname-expand \
     spiffy-directory-listing ssax sxml-serializer sxml-modifications sql-de-lite \
     srfi-19 refdb ini-file sparse-vectors z3 call-with-environment-variables hahn linenoise \
     crypt parley

+ iup canvas-draw logpro

Matt
-=-

On Thu, Apr 28, 2016 at 11:39 AM, Peter Bex <address@hidden> wrote:

Hello all,

The second release candidate for CHICKEN 4.11.0 is now available for download:
http://code.call-cc.org/dev-snapshots/2016/04/28/chicken-4.11.0rc2.tar.gz

This tarball has the following SHA-2 checksum:
7f88df077b24b756e2cd5e51dc71e9a4004d2ffb4c8560cdb9887b5a37490521

The list of changes since 4.10.0 is available here:
http://code.call-cc.org/dev-snapshots/2016/04/28/NEWS

The changes since the previous release candidate (rc1) are as follows:
- On 32-bit systems, the debugger client used incorrect printf format
   strings, resulting in invalid data used for the protocol.  This made
   debugging of programs running on 32-bit systems impossible (#1279).
- Under Mac OS X, "make check" failed in a non-installed CHICKEN due to
   the new "System Integrity Protection" breaking DYLD_LIBRARY_PATH in
   all processes that are invoked through /bin/sh (#1277).
   Thanks to J Irving for reporting this, and Jim Ursetto for creating
   and testing the fix.
- On 64-bit architectures where "char" defaults to unsigned (e.g. ARM64),
   negative signed fixnum literals embedded inside other literals would
   be decoded incorrectly (#1280).  Thanks to Alex Shendi for reporting
   this and testing the fix.
- When initializing a new egg repository, if the destination directory
   does not exist, chicken-install would write all files to the target
   as if it were a file.  Thanks to "LemonBoy" for reporting this and
   creating a fix.
- Stack checks inserted by the compiler would incorrectly trigger stack
   overflow errors after receiving a signal (#1283).  Thanks to
   "LemonBoy" for helping to track down this error.

These last-minute changes are very important for the stability of the
system, so we are very happy they made it in.  However, due to the impact
of especially the latter, we would ask you all to help us test the new
release candidate as thoroughly as the first one.

As usual, an easy way to test this RC is as follows:

$ make PLATFORM=<platform> PREFIX=<some dir> install check
$ <some dir>/bin/chicken-install pastiche

If you want to build CHICKEN with a compiler other than the default one,
just use C_COMPILER=<the compiler> (e.g., C_COMPILER=clang) on the make
invocation.

Of course, feel free to explore other supported build options (see the
README file for more information) and actually use CHICKEN 4.11.0rc2 for
your software.

If you can, please let us know the following information about the
environment you tested the RC tarball on:

Operating system: (e.g., FreeBSD 10.1, Debian 8, Windows 7 mingw-msys)
Hardware platform: (e.g., x86, x86-64, PPC)
C Compiler: (e.g., GCC 4.9.2, clang 3.6)
Installation works?: yes or no
Tests work?: yes or no
Installation of eggs works?: yes or no

Thanks in advance!

The CHICKEN Team

_______________________________________________
Chicken-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/chicken-users