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

2016-05-14 Thread 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  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= PREFIX= install check
> $ /bin/chicken-install pastiche
>
> If you want to build CHICKEN with a compiler other than the default one,
> just use C_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
>

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

2016-04-29 Thread J Irving 
Hey Peter

Thanks, and apologies for not getting around to testing with integrity
disabled. All good this time :)

Operating system: Mac OS X 10.11.4
Hardware platform: Intel Core i7
C Compiler: Apple LLVM version 7.3.0 (clang-703.0.29)
Installation works?: yes
Tests work?: yes
Installation of eggs works?: yes

   cheers, J
   2016-04-29 @ 16:54:38 -0400


* Peter Bex, on 2016-04-28 @ 18:39 +:
> 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= PREFIX= install check
> $ /bin/chicken-install pastiche
>
> If you want to build CHICKEN with a compiler other than the default one,
> just use C_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
> Chicken-users@nongnu.org
> https://lists.nongnu.org/mailman/listinfo/chicken-users



signature.asc
Description: PGP signature
___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users

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

2016-04-29 Thread Peter Bex 
On Thu, Apr 28, 2016 at 08:39:55PM +0200, Peter Bex wrote:
> If you can, please let us know the following information about the
> environment you tested the RC tarball on:

Replying to my own mail again, I've tested on a Raspberry Pi 2 (armv7l):

Operating system: Debian Jessie
Hardware platform: ARMv7 (32-bits)
C Compiler: clang 3.5.0
Installation works?: yes
Tests work?: yes
Installation of eggs works?: yes

Operating system: Debian Jessie
Hardware platform: ARMv7 (32-bits)
C Compiler: gcc 4.9.2
Installation works?: yes
Tests work?: yes
Installation of eggs works?: yes

Cheers,
Peter


signature.asc
Description: Digital signature
___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users

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

2016-04-28 Thread Bahman Movaqar 
On 04/28/2016 11:09 PM, Peter Bex 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

Operating system: Ubuntu 14.04
Hardware platform: x86_64
C Compiler: gcc (Ubuntu 4.8.4-2ubuntu1~14.04.1) 4.8.4
Installation works?: yes
Tests work?: yes
Installation of eggs works?: yes

Excellent job people!

--
Bahman Movaqar

http://BahmanM.com - https://twitter.com/bahman__m
https://github.com/bahmanm - https://gist.github.com/bahmanm
PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com)



signature.asc
Description: OpenPGP digital signature
___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users

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

2016-04-28 Thread Jeremy Steward 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello all, tested and verified the following:

Operating system: Debian Sid (unstable)
Hardware platform: x86 (Debian i686)
C Compiler: gcc version 5.3.1 20160424 (Debian 5.3.1-16)
Installation works?: yes
Tests work?: yes
Installation of eggs works?: yes

The following eggs were tested for installation:

* arrays
* matchable
* lazy-seq
* coops
* bind
* graphs
* utf8
* numbers
* readline
* hahn
* slime
* chicken-doc
* apropos
* make
* mini-kanren
* fmt
* format

- -- 
Jeremy Steward
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJXIoTZAAoJEHVwwAZUeZnZaPEP/ii+Jjivp2l88/xwodSzwGCT
NqPHGLk8NMcPo2Rh19WvCH4GcYEYBhwIuBmBZH/EyQZLCfzL1FGpJ/2xzzHSCLEL
ZI7gGxeVMWykA/7SD79Qeoz4rYN/401uqSf5ogbFOBdEgA0JSTiakIXPaa9atC1Z
8qljoqfpYxTLF5NC8+5Gh1VFFq8Kacgp5szl0/c4Pua7ZFMDKd/ZXtgrd7XldQgR
y3OHyXh8lIBgJ7gNzCT3crl31HLQrsxauqnlD97jSgnWt4KbH/2NvqB+fsnJ+PBt
KPgstzPFXChrFRPhNyMWvcpq1pZ4n0uRWlVgxengeJpehXQhDrQtpgdhM78bkR0x
v7YohcBnZGy7+LX4GrPZ6Ry5xUzd+7/Nq8HJRu6S4blud96KYBE3P6xsWZ4nMrJu
byNHYLgLvAQv+q+/CmwrzLxRYvA8VdNlBaxj4n5wQmhXlJvXcjM5VpYcnFWz7/Id
XY6GX87ypNGwHRMdf8cU/l8tmzIokFQjwv3BdpDe+/ej5klah7p8l7JmEhKYuu6o
salN9m+30QfRV2da0VV5KlVjdVpF1R/djv6ZBuUKSizivTwgLOCIf2x9dYFqqPqT
PmOIr3wMgMug5/LjOWTOrGXa0W7koEgvL9iyTPNGKvc/6BojhtlAtdDQKcM6XWUv
SiNqj+mFYVtVmjxGJkIH
=57Tq
-END PGP SIGNATURE-

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

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

2016-04-28 Thread Peter Bex 
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= PREFIX= install check
$ /bin/chicken-install pastiche

If you want to build CHICKEN with a compiler other than the default one,
just use C_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


signature.asc
Description: Digital signature
___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users