Re: [ANN] CHICKEN 5.3.0 release candidate available
On Thu, 12 Aug 2021 at 12:00, wrote: > Here's a suggested test procedure: > > $ make PREFIX= install check > $ /bin/chicken-install pastiche > I did the following in this order. make PREFIX=/usr/local PLATFORM=linux make PREFIX=/usr/local PLATFORM=linux check sudo make PREFIX=/usr/local PLATFORM=linux install sudo chicken-install pastiche Details in line. Operating system: Debian 11 > Hardware platform: x86 > C Compiler: GCC 10.2.1 > Installation works?: yes > Tests work?: yes > Installation of eggs works?: yes > -- Claude Marinier
Re: [Chicken-announce] [ANN] CHICKEN 5.3.0 release candidate available
Hi Christian, On Fri, 13 Aug 2021 09:22:10 +0200 (CEST) Christian Himpe wrote: > all seems to work, yet installing "sendfile", "http-session", "srfi-18" gave: > > ``` > Warning: Deprecated identifier `current-milliseconds' > ``` > > Otherwise: > > Operating system: Ubuntu Mate 20.04 > Hardware platform: x86-64 > C Compiler: gcc 10.3.0 > Installation works?: yes > Tests work?: yes > Installation of eggs works?: yes Thanks for the feedback. Regarding the warnings, they are unfortunate, but expected. `current-milliseconds' has been deprecated in favor of `current-process-milliseconds', but the latter is not available in previous versions of the 5.x series, so egg developers can't really just use `current-process-milliseconds' instead of `current-milliseconds' in 5.x. All the best. Mario -- http://parenteses.org/mario
Re: [ANN] CHICKEN 5.3.0 release candidate available
> On Sat, Aug 14, 2021 at 08:25:21PM +0200, Sven Hartrumpf wrote: > > Hi. > > > > The segmentation violation disappeared after cleaning my build script for > > chicken. > > (It contained an old "-mpreferred-stack-boundary=4" in > > C_COMPILER_OPTIMIZATION_OPTIONS, > > which I dropped now.) > > hm, I have to wonder: why does that break things? > More obscure C compiler options sometimes break working code, the possibility of interactions with optimzations and hardware contraints are endless. We also have alignment restrictions regarding stack-allocated floats, so perhaps there is something borked in that regard. I wouldn't worry too much about it, though. felix
Re: [ANN] CHICKEN 5.3.0 release candidate available
On Sat, Aug 14, 2021 at 08:25:21PM +0200, Sven Hartrumpf wrote: > Hi. > > The segmentation violation disappeared after cleaning my build script for > chicken. > (It contained an old "-mpreferred-stack-boundary=4" in > C_COMPILER_OPTIMIZATION_OPTIONS, > which I dropped now.) hm, I have to wonder: why does that break things? > So, the RC looks good to me. Thanks for double-checking! Cheers, Peter signature.asc Description: PGP signature
Re: [ANN] CHICKEN 5.3.0 release candidate available
Everything seems to be working, on all these: Operating system: Debian 11.0 (testing) on W10's WSL Hardware platform: x86-64 C Compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110 Operating system: Debian 11.0 (testing) Hardware platform: x86-64 C Compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110 Operating system: Raspberry Pi OS (Debian 10.10 (stable)) Hardware platform: aarch64 C Compiler: gcc (Debian 8.3.0-6) 8.3.0 Operating system: Raspbian (Debian 11.0 (testing)) Hardware platform: armv7l C Compiler: gcc (Raspbian 10.2.1-6+rpi1) 10.2.1 20210110 Not too much variety, but it's worth something! siiky
Re: [ANN] CHICKEN 5.3.0 release candidate available
Hi. The segmentation violation disappeared after cleaning my build script for chicken. (It contained an old "-mpreferred-stack-boundary=4" in C_COMPILER_OPTIMIZATION_OPTIONS, which I dropped now.) So, the RC looks good to me. Ciao Sven
Re: [Chicken-announce] [ANN] CHICKEN 5.3.0 release candidate available
I've tested on two of my systems, everything looks good to me. Operating system: Slackware64-current Hardware platform: x86-64 C Compiler: gcc (GCC) 10.3.0 Installation works?: yes Tests work?: yes Installation of eggs works?: yes Operating system: SlackwareARM-current Hardware platform: ARMv7 C Compiler: gcc (GCC) 10.2.0 Installation works?: yes Tests work?: yes Installation of eggs works?: yes On Thu, Aug 12, 2021 at 4:28 AM Peter Bex wrote: > Hello everyone, > > We are happy to announce the first release candidate of the upcoming > CHICKEN 5.3.0. > > CHICKEN 5.3.0rc1 is now available at this location: > https://code.call-cc.org/dev-snapshots/2021/08/12/chicken-5.3.0rc1.tar.gz > > The SHA256 sum of that tarball is > 61d59cb4f3ca226995d7dca3510c7a646c2cf1e28ebc771bf6c5177e28d14c81 > > This is bugfix release which takes care of several important issues. > > Irregex has been updated to the latest upstream (0.9.10), which fixes > a few issues with bol handling and irregex-replace/all with positive > lookbehind replaces all matches rather than just the first. > > A few bugs in the module system's handling of reexport have been fixed, > as well as a few bugs in the optimization of using argvector directly > in rest arguments, and a nasty issue where mutated parameters would be > reset if the mutation happened in a signal handler. > > A nice improvement is that to build CHICKEN, on most platforms you no > longer need to provide the PLATFORM variable to Make; we auto-detect > the platform you're building on. Of course, for cross-compilation > you'll still have to set it. > > Finally, we tweaked the garbage collector to avoid thrashing when the > heap was almost full. This should drastically improve performance for > certain usage patterns that trigger this pathological behaviour. > > The complete list of changes since version 5.2.0 is available here: > https://code.call-cc.org/dev-snapshots/2021/08/12/NEWS > > Please give it a test and report your findings to the mailing list. > > Here's a suggested test procedure: > > $ make 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 5.3.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 12.0, Debian 9, Windows 10 mingw-msys > under > mingw32) > Hardware platform: (e.g., x86, x86-64, PPC) > C Compiler: (e.g., GCC 6.4.0, clang 5.0.0) > Installation works?: yes or no > Tests work?: yes or no > Installation of eggs works?: yes or no > > Thanks in advance! > > The CHICKEN Team > -- Erik Falor Registered Linux User #445632 http://counter.li.org
Re: [ANN] CHICKEN 5.3.0 release candidate available
Tried again, ran my tests and everything seems to work. I'll keep poking at the rc and come back if I find anything. Thanks everyone! El 13 de agosto de 2021 6:00:33 a. m. GMT-03:00, "Jörg F. Wittenberger" escribió: >Hi Ariela, > >sorry, my bad. Looks like I got side tracked and never returned to >complete the release after merging the patch. > >Hope it works now. (Can't test myself currently.) > >/Jörg > >Am Fri, 13 Aug 2021 07:35:14 +0200 >schrieb Mario Domenech Goulart : > >> Hi Ariela, >> >> On Thu, 12 Aug 2021 21:44:11 -0300 Ariela Wenner >> wrote: >> >> > Hi all, I seem to be running into a weird issue with this rc when >> > trying to install the pigeon-hole egg (might happen with other eggs >> > too, I tested a bunch and it only happened with pigeon-hole though). >> > >> > Link to log output: >> > https://paste.call-cc.org/paste?id=96c654c6b97cd5268c6006e19c78739e19bbde42 >> > >> > Operating system: Debian testing and Debian stable >> > Hardware platform: x86-64 >> > C Compiler: GCC 10.2.1 >> > Installation works?: yes >> > Tests work?: yes >> > Installation of eggs works?: almost! >> > >> > Anyone else? >> >> pigeon-hole broke with b175ce65 in the chicken-core repository: >> http://salmonella-linux-x86.call-cc.org/master/clang/linux/x86/2021/04/12/yesterday-diff/ >> >> A patch has been submitted >> (https://github.com/0-8-15/pigeon-hole/pull/3) but a new version has >> not been released. >> >> In summary: it's an issue with pigeon-hole. >> >> All the best. >> Mario > -- Enviado desde mi dispositivo Android con K-9 Mail. Por favor, disculpa mi brevedad.
Re: [ANN] CHICKEN 5.3.0 release candidate available
Hi Ariela, sorry, my bad. Looks like I got side tracked and never returned to complete the release after merging the patch. Hope it works now. (Can't test myself currently.) /Jörg Am Fri, 13 Aug 2021 07:35:14 +0200 schrieb Mario Domenech Goulart : > Hi Ariela, > > On Thu, 12 Aug 2021 21:44:11 -0300 Ariela Wenner > wrote: > > > Hi all, I seem to be running into a weird issue with this rc when > > trying to install the pigeon-hole egg (might happen with other eggs > > too, I tested a bunch and it only happened with pigeon-hole though). > > > > Link to log output: > > https://paste.call-cc.org/paste?id=96c654c6b97cd5268c6006e19c78739e19bbde42 > > > > Operating system: Debian testing and Debian stable > > Hardware platform: x86-64 > > C Compiler: GCC 10.2.1 > > Installation works?: yes > > Tests work?: yes > > Installation of eggs works?: almost! > > > > Anyone else? > > pigeon-hole broke with b175ce65 in the chicken-core repository: > http://salmonella-linux-x86.call-cc.org/master/clang/linux/x86/2021/04/12/yesterday-diff/ > > A patch has been submitted > (https://github.com/0-8-15/pigeon-hole/pull/3) but a new version has > not been released. > > In summary: it's an issue with pigeon-hole. > > All the best. > Mario
Re: [Chicken-announce] [ANN] CHICKEN 5.3.0 release candidate available
Hi, all seems to work, yet installing "sendfile", "http-session", "srfi-18" gave: ``` Warning: Deprecated identifier `current-milliseconds' ``` Otherwise: Operating system: Ubuntu Mate 20.04 Hardware platform: x86-64 C Compiler: gcc 10.3.0 Installation works?: yes Tests work?: yes Installation of eggs works?: yes Best Christian - On Aug 12, 2021, at 12:28 PM, Peter Bex pe...@more-magic.net wrote: > Hello everyone, > > We are happy to announce the first release candidate of the upcoming > CHICKEN 5.3.0. > > CHICKEN 5.3.0rc1 is now available at this location: > https://code.call-cc.org/dev-snapshots/2021/08/12/chicken-5.3.0rc1.tar.gz > > The SHA256 sum of that tarball is > 61d59cb4f3ca226995d7dca3510c7a646c2cf1e28ebc771bf6c5177e28d14c81 > > This is bugfix release which takes care of several important issues. > > Irregex has been updated to the latest upstream (0.9.10), which fixes > a few issues with bol handling and irregex-replace/all with positive > lookbehind replaces all matches rather than just the first. > > A few bugs in the module system's handling of reexport have been fixed, > as well as a few bugs in the optimization of using argvector directly > in rest arguments, and a nasty issue where mutated parameters would be > reset if the mutation happened in a signal handler. > > A nice improvement is that to build CHICKEN, on most platforms you no > longer need to provide the PLATFORM variable to Make; we auto-detect > the platform you're building on. Of course, for cross-compilation > you'll still have to set it. > > Finally, we tweaked the garbage collector to avoid thrashing when the > heap was almost full. This should drastically improve performance for > certain usage patterns that trigger this pathological behaviour. > > The complete list of changes since version 5.2.0 is available here: > https://code.call-cc.org/dev-snapshots/2021/08/12/NEWS > > Please give it a test and report your findings to the mailing list. > > Here's a suggested test procedure: > > $ make 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 5.3.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 12.0, Debian 9, Windows 10 mingw-msys under > mingw32) > Hardware platform: (e.g., x86, x86-64, PPC) > C Compiler: (e.g., GCC 6.4.0, clang 5.0.0) > Installation works?: yes or no > Tests work?: yes or no > Installation of eggs works?: yes or no > > Thanks in advance! > > The CHICKEN Team -- Dr. rer. nat. Christian Himpe Computational Methods in Systems and Control Theory Max Planck Institute for Dynamics of Complex Technical Systems Sandtorstr. 1 39106 Magdeburg Germany https://himpe.science
Re: [ANN] CHICKEN 5.3.0 release candidate available
On Fri, Aug 13, 2021 at 08:18:39AM +0200, Sven Hartrumpf wrote: > Hi. > > gcc 10.3.0, amd64, Ubuntu 21.04 > > I am getting a new "Error: segmentation violation", when I add (time .) > around my main function mf call: > (time (mf (cons (car (argv)) (command-line-arguments > The error happens after this mf call is finished. > Worked for 5.2 (and earlier). > > I hope someone has a minimal example, because mine is huge. Hi Sven, Thanks for testing! Perhaps you can try compiling CHICKEN with DEBUGBUILD=1 and then re-compiling and running your program. This will add lots of inline checks, making the program run very slowly, but it will hopefully raise an early error rather than just segfaulting. This should make it easier to pinpoint where it's going wrong. Cheers, Peter signature.asc Description: PGP signature
Re: [ANN] CHICKEN 5.3.0 release candidate available
Hi. gcc 10.3.0, amd64, Ubuntu 21.04 I am getting a new "Error: segmentation violation", when I add (time .) around my main function mf call: (time (mf (cons (car (argv)) (command-line-arguments The error happens after this mf call is finished. Worked for 5.2 (and earlier). I hope someone has a minimal example, because mine is huge. BTW: the chicken-compiled binary is some percent faster than the one generated by 5.2. Ciao Sven
Re: [ANN] CHICKEN 5.3.0 release candidate available
Hi Ariela, On Thu, 12 Aug 2021 21:44:11 -0300 Ariela Wenner wrote: > Hi all, I seem to be running into a weird issue with this rc when trying to > install the pigeon-hole egg (might happen with other eggs too, I tested a > bunch > and it only happened with pigeon-hole though). > > Link to log output: > https://paste.call-cc.org/paste?id=96c654c6b97cd5268c6006e19c78739e19bbde42 > > Operating system: Debian testing and Debian stable > Hardware platform: x86-64 > C Compiler: GCC 10.2.1 > Installation works?: yes > Tests work?: yes > Installation of eggs works?: almost! > > Anyone else? pigeon-hole broke with b175ce65 in the chicken-core repository: http://salmonella-linux-x86.call-cc.org/master/clang/linux/x86/2021/04/12/yesterday-diff/ A patch has been submitted (https://github.com/0-8-15/pigeon-hole/pull/3) but a new version has not been released. In summary: it's an issue with pigeon-hole. All the best. Mario -- http://parenteses.org/mario
Re: [ANN] CHICKEN 5.3.0 release candidate available
On Thu, Aug 12, 2021 at 09:44:11PM -0300, Ariela Wenner wrote: > > Hi all, I seem to be running into a weird issue with this rc when trying to > install the pigeon-hole egg (might happen with other eggs too, I tested a > bunch > and it only happened with pigeon-hole though). > > Link to log output: > https://paste.call-cc.org/paste?id=96c654c6b97cd5268c6006e19c78739e19bbde42 Hi Ariela, Thanks for testing! It looks like the problem you ran into is caused by a bug in the egg that was always there, but got exposed by the changes we made to topological-sort. This has already been fixed in the egg's master branch but there doesn't seem to be a corresponding release for it. So I just filed this ticket with the egg maintainer: https://github.com/0-8-15/pigeon-hole/issues/4 Cheers, Peter signature.asc Description: PGP signature
Re: [ANN] CHICKEN 5.3.0 release candidate available
Hi all, I seem to be running into a weird issue with this rc when trying to
install the pigeon-hole egg (might happen with other eggs too, I tested a bunch
and it only happened with pigeon-hole though).
Link to log output:
https://paste.call-cc.org/paste?id=96c654c6b97cd5268c6006e19c78739e19bbde42
Operating system: Debian testing and Debian stable
Hardware platform: x86-64
C Compiler: GCC 10.2.1
Installation works?: yes
Tests work?: yes
Installation of eggs works?: almost!
Anyone else?
On Thu, 12 Aug 2021 12:28:23 +0200
Peter Bex wrote:
> Hello everyone,
>
> We are happy to announce the first release candidate of the upcoming
> CHICKEN 5.3.0.
>
> CHICKEN 5.3.0rc1 is now available at this location:
> https://code.call-cc.org/dev-snapshots/2021/08/12/chicken-5.3.0rc1.tar.gz
>
> The SHA256 sum of that tarball is
> 61d59cb4f3ca226995d7dca3510c7a646c2cf1e28ebc771bf6c5177e28d14c81
>
> This is bugfix release which takes care of several important issues.
>
> Irregex has been updated to the latest upstream (0.9.10), which fixes
> a few issues with bol handling and irregex-replace/all with positive
> lookbehind replaces all matches rather than just the first.
>
> A few bugs in the module system's handling of reexport have been fixed,
> as well as a few bugs in the optimization of using argvector directly
> in rest arguments, and a nasty issue where mutated parameters would be
> reset if the mutation happened in a signal handler.
>
> A nice improvement is that to build CHICKEN, on most platforms you no
> longer need to provide the PLATFORM variable to Make; we auto-detect
> the platform you're building on. Of course, for cross-compilation
> you'll still have to set it.
>
> Finally, we tweaked the garbage collector to avoid thrashing when the
> heap was almost full. This should drastically improve performance for
> certain usage patterns that trigger this pathological behaviour.
>
> The complete list of changes since version 5.2.0 is available here:
> https://code.call-cc.org/dev-snapshots/2021/08/12/NEWS
>
> Please give it a test and report your findings to the mailing list.
>
> Here's a suggested test procedure:
>
> $ make 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 5.3.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 12.0, Debian 9, Windows 10 mingw-msys under
> mingw32)
> Hardware platform: (e.g., x86, x86-64, PPC)
> C Compiler: (e.g., GCC 6.4.0, clang 5.0.0)
> Installation works?: yes or no
> Tests work?: yes or no
> Installation of eggs works?: yes or no
>
> Thanks in advance!
>
> The CHICKEN Team
--
#!/usr/bin/scheme --script
(for-each (lambda (line) (display line) (newline))
'("We don't need no iteration"
"We don't need no flow control"
"No more garbage in the call stack"
"Hey! Did you leave the args alone?"
"All in all it's just an optimized tail call."
""
"We don't need no side-effecting"
"We don't need no constructors"
"No more NullPointerExceptions"
"Hey! Juniors! Leave that source alone!"
"All in all it's just a pure Scheme function call."))
[ANN] CHICKEN 5.3.0 release candidate available
Hello everyone, We are happy to announce the first release candidate of the upcoming CHICKEN 5.3.0. CHICKEN 5.3.0rc1 is now available at this location: https://code.call-cc.org/dev-snapshots/2021/08/12/chicken-5.3.0rc1.tar.gz The SHA256 sum of that tarball is 61d59cb4f3ca226995d7dca3510c7a646c2cf1e28ebc771bf6c5177e28d14c81 This is bugfix release which takes care of several important issues. Irregex has been updated to the latest upstream (0.9.10), which fixes a few issues with bol handling and irregex-replace/all with positive lookbehind replaces all matches rather than just the first. A few bugs in the module system's handling of reexport have been fixed, as well as a few bugs in the optimization of using argvector directly in rest arguments, and a nasty issue where mutated parameters would be reset if the mutation happened in a signal handler. A nice improvement is that to build CHICKEN, on most platforms you no longer need to provide the PLATFORM variable to Make; we auto-detect the platform you're building on. Of course, for cross-compilation you'll still have to set it. Finally, we tweaked the garbage collector to avoid thrashing when the heap was almost full. This should drastically improve performance for certain usage patterns that trigger this pathological behaviour. The complete list of changes since version 5.2.0 is available here: https://code.call-cc.org/dev-snapshots/2021/08/12/NEWS Please give it a test and report your findings to the mailing list. Here's a suggested test procedure: $ make 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 5.3.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 12.0, Debian 9, Windows 10 mingw-msys under mingw32) Hardware platform: (e.g., x86, x86-64, PPC) C Compiler: (e.g., GCC 6.4.0, clang 5.0.0) 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: PGP signature
