Re: [Chicken-users] CHICKEN 4.10.0 has been released - apply check hangs
Hi, I finally ungraded Debian from Wheezy to Jessie (pleasantly uneventful); this upgraded gcc to version 4.9.2. Built chicken 4.10.0 and the check hangs as expected (apply test); built with clang and all is well. Switched to MinGW W64 in MS Windows Vista and build chicken 4.10.0 without problem; even the check works well (does not hang). MinGW W64 provides gcc version 5.1.0. gcc (i686-posix-dwarf-rev0, Built by MinGW-W64 project) 5.1.0 This in interesting because it differs from Matt Gushee's experience. On Mon, 27 Jul 2015, Matt Gushee wrote: Operating system: Arch Linux Hardware platform: x86-64 C Compiler: gcc 5.1.0 Installation works?: yes Tests work?: no [hangs on apply-test.scm] -- Claude Marinier ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] CHICKEN 4.10.0 has been released
On Fri, Aug 7, 2015 at 04:53, Peter Bex wrote: On Fri, Aug 07, 2015 at 09:54:22AM +0200, Christian Kellermann wrote: * Claude Marinier [150806 20:15]: Note that I did not have this problem with the release candidates. Could you try with them again and tell me exactly which one worked? Because there are no differences that touch code between the rc4 and the 4.10.0 version in git. If there are differences in behaviour for you this could mean we shipped a rc with broken pregenerated C code for whatever reason and I'd like to investigate that. I agree, this is somewhat worrying. One problem with MINGW is that it's badly maintained (unless I'm mistaken, the most recent binary release is from 2013). Mingw-w64 is better maintained, and despite the name it also works on 32 bit systems. I think it does support getc_unlocked. You can find it here: http://mingw-w64.org Hi, Building both 4.10.0 and rc4 with the MinGW installation on the Windows 7 64-bit PC at work produces the same error : undefined reference to `getc_unlocked'. This was from a DOS box (clink) without MSYS. Building on rc4 on the same PC with mingw-w64 works without error (also without MSYS). Check works as expected as does numbers egg installation. I have had problems with MinGW and re-installed a couple of times. I am growing less confident in these installations. This is a good time to move to mingw-w64; I will try it at home later today. Is it useful to dig deeper into the problem with the old MinGW or should I just drop it? Thanks. -- Claude Marinier ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] CHICKEN 4.10.0 has been released
On Fri, Aug 07, 2015 at 09:54:22AM +0200, Christian Kellermann wrote: * Claude Marinier claudem...@gmail.com [150806 20:15]: Note that I did not have this problem with the release candidates. Could you try with them again and tell me exactly which one worked? Because there are no differences that touch code between the rc4 and the 4.10.0 version in git. If there are differences in behaviour for you this could mean we shipped a rc with broken pregenerated C code for whatever reason and I'd like to investigate that. I agree, this is somewhat worrying. One problem with MINGW is that it's badly maintained (unless I'm mistaken, the most recent binary release is from 2013). Mingw-w64 is better maintained, and despite the name it also works on 32 bit systems. I think it does support getc_unlocked. You can find it here: http://mingw-w64.org 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] CHICKEN 4.10.0 has been released
* Claude Marinier claudem...@gmail.com [150806 20:15]: Note that I did not have this problem with the release candidates. Could you try with them again and tell me exactly which one worked? Because there are no differences that touch code between the rc4 and the 4.10.0 version in git. If there are differences in behaviour for you this could mean we shipped a rc with broken pregenerated C code for whatever reason and I'd like to investigate that. Kind regards, Christian -- May you be peaceful, may you live in safety, may you be free from suffering, and may you live with ease. ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] CHICKEN 4.10.0 has been released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I'll just chime in here on the side, but I believe I made an edit to the wiki quite some time ago about switching to mingw-64, since at the time I had some issues using the bind egg. Moreover, while I have not tested CHICKEN 4.10 yet, I compiled CHICKEN 4.9.1 myself on cygwin64 with no error,so it's unlikely any changes need to be made on that front. Cheers, - -- Jeremy Steward -BEGIN PGP SIGNATURE- Version: APG v1.1.1 iQJDBAEBCgAtBQJVxL4OJhxKZXJlbXkgU3Rld2FyZCA8amVyZW15QHRoYXRnZW9n dXkuY2E+AAoJEHVwwAZUeZnZNokP/0lLRxE0YimQuLmPt/P4lwXTaIejJMwbC8gB Cq9SBby8a+EoO5bsjaAxgZH+JTr8T00eESBogqkvFIt+0AWqAFcNvAcEv6/Z/Jg7 ecyHYmIe1CYlDZlAVMHznGacR48ga9G9eNK5xz3svIacLtWv2xTJwbxZntDLTR8K Fdg9MeeyBGcSVtrZMVE89q4F24v2Q2P3KP8BcrSU46LaDAhKqxDJTDPpIjYnnUQW Bx9HW29zA8XI5RFCUlDrY5RbApPeKHpbnfD1LCMDTY0ktzFRyEU9UkXBVUVZZiz4 4tjBu0c/95C6q7S5YruCESC275vlOlPXWI2OKMsiaYK77tSkToHqGSx3ArrGMWxE zP8EppAvfkB8wvulXhVtbmL+i09sAO7DpBXxQNeSdqou0QmWo4pmqT6YCxEw8zoE ANDfFFc3rJMGdwGg0Qb0NHqJhPiKqdcNsSTj9uJZa2pO08glXz5QHhMTx/yG3IWz 6AUWsJVj7JGJaALXL1p0wHtDdxdY7KeHwcRBGRuGwDFj5xi6r0dI2Z9aga8zbVGb GkHVZ6gXuKoSTBM0Q3zCsSBjjsGD6biBG+WGfM39JuKxQ+4oUqQu4c8CUhUx8pAP vXhD5ODyiE/rrBux0SVfuY+n5k/SaZFDMo0tb8P5gAO62WLyRzuzMtHT+1BTmbNB AGz9bDRY =SZ2n -END PGP SIGNATURE- ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] CHICKEN 4.10.0 has been released
On Fri, Aug 07, 2015 at 04:08:49PM +0200, Christian Kellermann wrote: Claude Marinier claudem...@gmail.com writes: Is it useful to dig deeper into the problem with the old MinGW or should I just drop it? If you aren't sure about the configuration you experienced the error in I think it's better not to waste time and effort on finding out what went wrong here, unless you yourself are curious. I think we should recommend using mingw-64 for CHICKEN instead. Peter, what do you think? If by the next release mingw has no new release, I think it's a good idea to add it to the README. But before doing so I have to verify what I'm using in my VM at home; maybe it is mingw32 after all. In that case I wonder what the difference is. 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] CHICKEN 4.10.0 has been released
Jeremy Steward jer...@thatgeoguy.ca writes: Moreover, while I have not tested CHICKEN 4.10 yet, I compiled CHICKEN 4.9.1 myself on cygwin64 with no error,so it's unlikely any changes need to be made on that front. Note that cygwin comes with a current CHICKEN package :) -- May you be peaceful, may you live in safety, may you be free from suffering, and may you live with ease. ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] CHICKEN 4.10.0 has been released
Claude Marinier claudem...@gmail.com writes: Building on rc4 on the same PC with mingw-w64 works without error (also without MSYS). Check works as expected as does numbers egg installation. I have had problems with MinGW and re-installed a couple of times. I am growing less confident in these installations. This is a good time to move to mingw-w64; I will try it at home later today. Is it useful to dig deeper into the problem with the old MinGW or should I just drop it? If you aren't sure about the configuration you experienced the error in I think it's better not to waste time and effort on finding out what went wrong here, unless you yourself are curious. I think we should recommend using mingw-64 for CHICKEN instead. Peter, what do you think? Christian -- May you be peaceful, may you live in safety, may you be free from suffering, and may you live with ease. ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] CHICKEN 4.10.0 has been released
Peter Bex scripsit: One problem with MINGW is that it's badly maintained (unless I'm mistaken, the most recent binary release is from 2013). Mingw-w64 is better maintained, and despite the name it also works on 32 bit systems. I think it does support getc_unlocked. You can find it here: http://mingw-w64.org As part of the Chicken 5 effort, we should consider switching not only to mingw-w64, but also to MSYS2. We should also look at Cygwin-64, as there are probably still parts of the code base that assume that Cygwin is inherently 32-bit. (I'm not using Cygwin-64 yet myself, so there is no hurry on this.) -- John Cowan http://www.ccil.org/~cowanco...@ccil.org He made the Legislature meet at one-horse tank-towns out in the alfalfa belt, so that hardly nobody could get there and most of the leaders would stay home and let him go to work and do things as he pleased. --H.L. Mencken's translation of the Declaration of Independence ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] CHICKEN 4.10.0 has been released
On Wed, 5 Aug 2015 16:46:17, Claude Marinier wrote: On 4 August 2015 at 21:52, Peter Bex wrote: We are pleased to announce the immediate availability of CHICKEN 4.10.0 at the following URL: http://code.call-cc.org/releases/4.10.0/chicken-4.10.0.tar.gz Hi, Had trouble with this release on MS Windows Vista (32-bit). Re-installed MinGW and tried again. Tried both from bash in MSYS and Windows' cmd. If works for a while before dying. Here is the relevant portion. gcc -Wl,--enable-auto-import -shared -Wl,--out-implib,libchicken.dll.a \ -o libchicken.dll library.o eval.o data-structures.o ports.o files.o extras.o lolevel.o utils.o tcp.o srfi-1.o srfi-4.o srfi-13.o srfi-14.o srfi-18.o srfi-69.o posixwin.o irregex.o scheduler.o profiler.o stub.o expand.o modules.o chicken-syntax.o chicken-ffi-syntax.o build-version.o runtime.o apply-hack.x86.o -lm -lws2_32 library.o:library.c:(.text+0x342b8): undefined reference to `getc_unlocked' library.o:library.c:(.text+0x34310): undefined reference to `getc_unlocked' library.o:library.c:(.text+0x3433e): undefined reference to `getc_unlocked' c:/mingw/bin/../lib/gcc/mingw32/4.8.1/../../../../mingw32/bin/ld.exe: library.o: badreloc address 0x0 in section `.data' collect2.exe: error: ld returned 1 exit status make: *** [libchicken.dll] Error 1 Complete output available if needed. Thanks. Hi, The patch attached to the following message fixes the problem. http://lists.gnu.org/archive/html/chicken-users/2015-04/msg00044.html Note that I did not have this problem with the release candidates. Thanks. P.S. I appologise for the superfluous quoting in the previous message. I am still uncomfortable with these GUI mail tools. I miss alpine. :-( -- Claude Marinier ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] CHICKEN 4.10.0 has been released
On 4 August 2015 at 21:52, Peter Bex pe...@more-magic.net wrote: We are pleased to announce the immediate availability of CHICKEN 4.10.0 at the following URL: http://code.call-cc.org/releases/4.10.0/chicken-4.10.0.tar.gz Hi, Had trouble with this release on MS Windows Vista (32-bit). Re-installed MinGW and tried again. Tried both from bash in MSYS and Windows' cmd. If works for a while before dying. Here is the relevant portion. gcc -Wl,--enable-auto-import -shared -Wl,--out-implib,libchicken.dll.a \ -o libchicken.dll library.o eval.o data-structures.o ports.o files.o extras.o lolevel.o utils.o tcp.o srfi-1.o srfi-4.o srfi-13.o srfi-14.o srfi-18.o srfi-69.o posixwin.o irregex.o scheduler.o profiler.o stub.o expand.o modules.o chicken-syntax.o chicken-ffi-syntax.o build-version.o runtime.o apply-hack.x86.o -lm -lws2_32 library.o:library.c:(.text+0x342b8): undefined reference to `getc_unlocked' library.o:library.c:(.text+0x34310): undefined reference to `getc_unlocked' library.o:library.c:(.text+0x3433e): undefined reference to `getc_unlocked' c:/mingw/bin/../lib/gcc/mingw32/4.8.1/../../../../mingw32/bin/ld.exe: library.o: badreloc address 0x0 in section `.data' collect2.exe: error: ld returned 1 exit status make: *** [libchicken.dll] Error 1 Complete output available if needed. Thanks. This tarball has the following SHA256 checksum: 0e07f5abcd11961986950dbeaa5a40db415f8a1b65daff9c300e9b05b334899b This is mostly a bugfix release, containing quite a lot of accumulated bug fixes but relatively few new features. Nevertheless, there are a great many changes in this release since 4.9.0. It has three security bugfixes: for CVE-2014-6310, CVE-2014-9651 and CVE-2015-4556. Another important security-related cleanup/improvement is related to path expansion: many file procedures in CHICKEN used to automatically and implicitly convert paths containing tilde (~) characters to $HOME, and expand shell variables. This behaviour was deprecated in 4.9.0, and has now been removed, in favor of the pathname-expand egg. A few of the build variables have been renamed, so if you have a custom build script, please review the NEWS file carefully. Other notable changes: * The performance of reading and writing SRFI-4 u8vectors has been substantially improved. * Various bugs in the functors implementation have been fixed, making them better usable. * chicken.h can once more be correctly compiled with a C++ compiler. * The -r5rs-syntax flag has been fixed to enforce r5rs syntax. For the full list of changes, see http://code.call-cc.org/releases/4.10.0/NEWS-4.10.0 Many thanks to all of you who have helped to test the release candidates, provided bug reports, feedback and improvements. Kind regards, The CHICKEN Team -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 490 bytes Desc: Digital signature URL: http://lists.nongnu.org/archive/html/chicken-users/attachments/20150804/b3530e99/attachment.pgp -- Message: 3 Date: Wed, 5 Aug 2015 09:09:57 +0200 From: Christian Kellermann ck...@pestilenz.org To: chicken-users@nongnu.org Cc: chicken-annou...@nongnu.org Subject: [Chicken-users] [ICC 2015] Reminder for T-Shirts Message-ID: 20150805070957.gb10...@pestilenz.org Content-Type: text/plain; charset=us-ascii Hello! As I have written before I will be organising another round of CHICKEN T-Shirt prints. To put that plan into action I need a rough idea on how many shirts should be made and of course which size will fit you! So this is your friendly reminder that you need to tell me your shirt sizes! The laudable andyjpb has been the first and only responder so far on the wiki page. If your shirt size is a secret please mail me the wanted size and quantity. The final prize for each shirt depends on the overall amount. So there will be a deadline for orders and it's August 18th midnight UTC. So get up, rip your shirt off and look at the label in the back, maybe adjust the size and tell me! The place in the wiki is the shirts section on http://wiki.call-cc.org/event/intercontinental-chicken-conference-2015 Kind regards, Christian P.S.: You may put your shirts back on now, thanks. -- May you be peaceful, may you live in safety, may you be free from suffering, and may you live with ease. -- Message: 4 Date: Wed, 05 Aug 2015 10:11:15 -0400 From: Nick Andryshak nandrys...@gmail.com To: chicken-users@nongnu.org Subject: [Chicken-users] What use, if any, is `any?' ? Message-ID: oirr3nhomf0@gmail.com Content-Type: text/plain Hello! I came across this function in the official documentation recently: http://wiki.call-cc.org/man/4/Unit%20data-structures#any any? [procedure] (any? X) Ignores its argument and always returns #t. This is actually useful sometimes. Is it, though?
