Re: [Chicken-hackers] will we have a release this year?
Hi, The environments egg will not work under Chicken 4.7.4 and later, due to changes in the internal representation (also noted in the documentation). The rewrite branch is meant to fix this issue. This was an error from the rewrite branch. We were wondering whether an internal error such as the one reported would be from chicken or the egg. Regards, @ndy -- andy...@ashurst.eu.org http://www.ashurst.eu.org/ 0x7EBA75FF ___ Chicken-hackers mailing list Chicken-hackers@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-hackers
Re: [Chicken-hackers] will we have a release this year?
Hi, I have been testing 4.8.0rc4 quite a bit this week, and everything seems to work fine, so if there are no objections, I will make the release next Monday. Did people see my bug report on chicken-users regarding the environments egg and eval? I posted in the Re: [Chicken-users] Chicken 4.8.0 release candidate 4 now available thread on 2012/09/18. -- Another was segfaulting and continued to segfault on 'load'. I narrowed it down to this repro case in the interpreter: - #;1 (use environments) #;2 (define widget-eval-env (make-parameter (environment-copy (scheme-report-environment 5) #t))) - Using Mortiz's rewrite branch of the environments egg: https://anonymous:@code.call-cc.org/svn/chicken-eggs/release/4/environments/branches/rewrite/ ... stops the segfault. I can get a binary out but it throws an exception somewhere it didn't used to: - unbound variable ##sys#list - ...and my debugging efforts so far point to a problem with eval and an environment from the environments egg. -- Regards, @ndy -- andy...@ashurst.eu.org http://www.ashurst.eu.org/ 0x7EBA75FF ___ Chicken-hackers mailing list Chicken-hackers@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-hackers
Re: [Chicken-hackers] will we have a release this year?
Hi Andy, The environments egg will not work under Chicken 4.7.4 and later, due to changes in the internal representation (also noted in the documentation). The rewrite branch is meant to fix this issue. Ivan On Sep 23, 2012 10:09 PM, Andy Bennett andy...@ashurst.eu.org wrote: Hi, I have been testing 4.8.0rc4 quite a bit this week, and everything seems to work fine, so if there are no objections, I will make the release next Monday. Did people see my bug report on chicken-users regarding the environments egg and eval? I posted in the Re: [Chicken-users] Chicken 4.8.0 release candidate 4 now available thread on 2012/09/18. -- Another was segfaulting and continued to segfault on 'load'. I narrowed it down to this repro case in the interpreter: - #;1 (use environments) #;2 (define widget-eval-env (make-parameter (environment-copy (scheme-report-environment 5) #t))) - Using Mortiz's rewrite branch of the environments egg: https://anonymous:@code.call-cc.org/svn/chicken-eggs/release/4/environments/branches/rewrite/ ... stops the segfault. I can get a binary out but it throws an exception somewhere it didn't used to: - unbound variable ##sys#list - ...and my debugging efforts so far point to a problem with eval and an environment from the environments egg. -- Regards, @ndy -- andy...@ashurst.eu.org http://www.ashurst.eu.org/ 0x7EBA75FF ___ Chicken-hackers mailing list Chicken-hackers@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-hackers
Re: [Chicken-hackers] will we have a release this year?
Thanks for all the release work! I am happy to report a successful installation with gcc 4.7.2 (released some hours ago), Linux, 64bit. Sven ___ Chicken-hackers mailing list Chicken-hackers@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-hackers
Re: [Chicken-hackers] will we have a release this year?
From: Ivan Raikov ivan.g.rai...@gmail.com Subject: Re: [Chicken-hackers] will we have a release this year? Date: Fri, 21 Sep 2012 22:10:02 +0900 Hi all, I have been testing 4.8.0rc4 quite a bit this week, and everything seems to work fine, so if there are no objections, I will make the release next Monday. cheers cheers, felix ___ Chicken-hackers mailing list Chicken-hackers@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-hackers
Re: [Chicken-hackers] will we have a release this year?
On Fri, 14 Sep 2012 19:38:46 +0200 (CEST) Felix fe...@call-with-current-continuation.org wrote: From: Ivan Raikov ivan.g.rai...@gmail.com Subject: Re: [Chicken-hackers] will we have a release this year? Date: Fri, 14 Sep 2012 10:54:55 +0900 Since you are getting bored and we wouldn't want you to switch to C# or anything like this, perhaps I can just make the release after you are done with the keyword reading fix? This is already the Most Tested Release Candidate of Chicken Ever, so a release can be made with (some) confidence ;-) That was what I wanted to suggest. We only need the keyword fix signed off and wait for a salmonella run. The keyword fix has been pushed and salmonella doesn't show anything abnormal today: http://tests.call-cc.org/master/linux/x86/2012/09/15/yesterday-diff/ So, I think we are ready to release. Best wishes. Mario -- http://parenteses.org/mario ___ Chicken-hackers mailing list Chicken-hackers@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-hackers
[Chicken-hackers] will we have a release this year?
Hi! I'm slowly getting bored with this endless bugfixing. Can I make a new release candidate, please? The one open bug is the keyword reading stuff, a patch is pending. The OpenBSD bugs are 1) obscure and long known (symbol-GC test), or 2) non-critical and caused by politically correct compiler-warnings (scrutiny-test failure), which I do not see as something that should block a release. The sh-stuff reported by Claude is also nothing too serious, so let's get on with it, I want to take a break. cheers, felix ___ Chicken-hackers mailing list Chicken-hackers@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-hackers
Re: [Chicken-hackers] will we have a release this year?
* felix winkelmann fe...@call-with-current-continuation.org [120913 21:13]: Hi! I'm slowly getting bored with this endless bugfixing. Can I make a new release candidate, please? The one open bug is the keyword reading stuff, a patch is pending. The OpenBSD bugs are 1) obscure and long known (symbol-GC test), or 2) non-critical and caused by politically correct compiler-warnings (scrutiny-test failure), which I do not see as something that should block a release. The sh-stuff reported by Claude is also nothing too serious, so let's get on with it, I want to take a break. I agree. -- Be right back -- Godot. ___ Chicken-hackers mailing list Chicken-hackers@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-hackers
