[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Chicken-announce] [Chicken-users] [ANN] CHICKEN 4.11.0 release cand

From: Timo Myyrä
Subject: Re: [Chicken-announce] [Chicken-users] [ANN] CHICKEN 4.11.0 release candidate 1 available
Date: Wed, 06 Apr 2016 07:30:17 +0300
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (berkeley-unix)

Peter Bex <address@hidden> writes:

> Hello everyone,
> we are happy to announce the first release candidate of the upcoming
> CHICKEN 4.11.0. It is now available at this location:
> The SHA 256 sum of that tarball is
> d7da097fb886ca2b70ae5bf2510ee40bf57a0453c0aaaf203de648951b24a751
> The list of changes since version 4.10.0 is available here:
> Please give it a test and report your findings to the mailing list.
> Here's a suggested test procedure:
>   $ 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.0rc1 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


Great work on the new release, hope to see Chicken 5 soon.

Operating system: OpenBSD-current
Hardware platform: x86-64
C Compiler: GCC 4.2,1
Installation works?: yes
Tests work?: yes [3/4 times]
Installation of eggs works?: yes

My first test run crashed on signal tests. Sadly I didn't copy the test output. 
I re-run the tests for 3 times
to see if it would re-appear but so far all later test runs have succeeded.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]