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 +0000: > 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 > 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
