Re: [Chicken-users] [PATCH] Make library tests compare numbers within epsilon [Was Re: Is chicken supported on 32 bit Linux?]
Thanks Sven and Peter, the make and install and check targets all finish without errors with -O3 under gcc 4.7.1! /jl Could you try whether make check on a -O3-compiled CHICKEN succeeds with the attached patch? Cheers, Peter -- ASCII ribbon campaign ( ) Powered by Lemote Fuloong against HTML e-mail X Loongson MIPS and OpenBSD and proprietary/ \http://www.mutt.org attachments / \ Code Blue or Go Home! Encrypted email preferred PGP Key 2048R/DA65BC04 ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
[Chicken-users] Is chicken supported on 32 bit Linux?
On the latest stable 4.8.0.3: Is chicken supported on 32 bit Linux systems? The make and make install went fine but make check blew up early. Looking over the mailing list archives somebody else got the same problem way back when and realized it was because of some x86_64 test case but nobody ever said whether the tests are broken or whether this requires 64 bit support. Can somebody make a definitive comment on this please? If this is supposed to work I'll run it again and post the output. Thanks /jl -- ASCII ribbon campaign ( ) Powered by Lemote Fuloong against HTML e-mail X Loongson MIPS and OpenBSD and proprietary/ \http://www.mutt.org attachments / \ Code Blue or Go Home! Encrypted email preferred PGP Key 2048R/DA65BC04 ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Is chicken supported on 32 bit Linux?
Hi Christian, Here's the part of the test that crashed. If you need the prior stuff just let me know, I didn't want to post too hugely to the list! Thanks! /jl library tests ... ../chicken library-tests.scm -output-file a.c -verbose -include-path .. -specialize Warning: in local unknown procedure, in local unknown procedure, in toplevel unknown procedure: (library-tests.scm:27) in procedure call to `finite?', expected argument #1 of type `number', but was given an argument of type `symbol' Warning: in local unknown procedure, in local unknown procedure, in toplevel unknown procedure: (library-tests.scm:51) in procedure call to `exact?', expected argument #1 of type `number', but was given an argument of type `symbol' Warning: in local unknown procedure, in local unknown procedure, in toplevel unknown procedure: (library-tests.scm:55) in procedure call to `inexact?', expected argument #1 of type `number', but was given an argument of type `symbol' Warning: in local unknown procedure, in local unknown procedure, in toplevel unknown procedure: (library-tests.scm:95) in procedure call to `even?', expected argument #1 of type `number', but was given an argument of type `symbol' Warning: in local unknown procedure, in local unknown procedure, in toplevel unknown procedure: (library-tests.scm:96) in procedure call to `odd?', expected argument #1 of type `number', but was given an argument of type `symbol' Warning: in local unknown procedure, in local unknown procedure, in toplevel unknown procedure: (library-tests.scm:167) in procedure call to `min', expected argument #1 of type `number', but was given an argument of type `symbol' Warning: in local unknown procedure, in local unknown procedure, in toplevel unknown procedure: (library-tests.scm:168) in procedure call to `max', expected argument #1 of type `number', but was given an argument of type `symbol' gcc a.c -o a.o -c -fno-strict-aliasing -fwrapv -DHAVE_CHICKEN_CONFIG_H -DC_ENABLE_PTABLES -O3 -fomit-frame-pointer -I.. -I/usr/local/include/chicken rm a.c gcc a.o -o a.out -L.. -L/usr/local/lib -Wl,-R/usr/local/lib -lchicken -lm -ldl rm a.o Error: (library-tests.scm:210) assertion failed: (= (sin 42.0) (fpsin 42.0)) Call history: library-tests.scm:198: number-string library-tests.scm:198: g846 library-tests.scm:198: number-string library-tests.scm:198: g846 library-tests.scm:198: number-string library-tests.scm:198: g846 library-tests.scm:198: number-string library-tests.scm:198: g846 library-tests.scm:198: number-string library-tests.scm:198: g846 library-tests.scm:198: number-string library-tests.scm:198: g846 library-tests.scm:198: number-string library-tests.scm:198: g846 library-tests.scm:198: number-string library-tests.scm:210: ##sys#error -- make[1]: *** [check] Error 70 make[1]: Leaving directory `/home/dev01/builds/chicken-4.8.0.3' make: *** [check] Error 2 ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Is chicken supported on 32 bit Linux?
On Tue, May 28, 2013 at 04:36:11PM +0200, Christian Kellermann wrote: * John Long codeb...@inbox.lv [130528 16:25]: Hi Christian, Here's the part of the test that crashed. If you need the prior stuff just let me know, I didn't want to post too hugely to the list! Yes, some more info would be nice. Did you just download the 4.8.0.3 tarball untarred it, ran make make install make check? Yes, except I didn't know how to tell the makefile to use -O3 so I changed the C_COMPILER_OPTIMIZATION_OPTIONS after the else in Makefile.linux to match the line before the else. What have been your build steps? make PLATFORM=linux su make PLATFORM=linux install ctrl-d to exit to user shell make PLATFORM=linux check What should I attach? Thanks /jl ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Is chicken supported on 32 bit Linux?
On Tue, May 28, 2013 at 02:36:58PM +, Mario Domenech Goulart wrote: Hey John On Tue, 28 May 2013 14:25:09 + John Long codeb...@inbox.lv wrote: Warning: in local unknown procedure, in local unknown procedure, in toplevel unknown procedure: (library-tests.scm:168) in procedure call to `max', expected argument #1 of type `number', but was given an argument of type `symbol' gcc a.c -o a.o -c -fno-strict-aliasing -fwrapv -DHAVE_CHICKEN_CONFIG_H -DC_ENABLE_PTABLES -O3 -fomit-frame-pointer -I.. -I/usr/local/include/chicken rm a.c gcc a.o -o a.out -L.. -L/usr/local/lib -Wl,-R/usr/local/lib -lchicken -lm -ldl How did you call make to build, install and check chicken? make PLATFORM=linux su make PLATFORM=linux install exit make PLATFORM=linux check Do you have libchicken.so in /usr/local/lib? Yes, it is a symlink to libchicken.so.6 also in /usr/local/lib If so, is it the one installed by chicken-4.8.0.3? Yes, it has today's date and time on it. Thanks. ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Is chicken supported on 32 bit Linux?
On Tue, May 28, 2013 at 04:49:48PM +0200, Peter Bex wrote: On Tue, May 28, 2013 at 02:25:09PM +, John Long wrote: Hi Christian, Here's the part of the test that crashed. If you need the prior stuff just let me know, I didn't want to post too hugely to the list! Error: (library-tests.scm:210) assertion failed: (= (sin 42.0) (fpsin 42.0)) fpsin expands pretty much to a direct call to the C sin() function, while sin is wrapped in a function. It could be that your compiler is performing some optimization which causes this value to be (slightly?) different. It sounds like you nailed it. The tests run fine at -Os but fail at -O2 and -O3. If it's possible, could you try it on a different version of your C compiler (or another C compiler entirely), and/or tell us your compiler's version? It's vanilla gcc 4.7.1. I'm ok for now but I would like it to work at least at -O2. Seems like gcc (almost) always works at -O2! /jl ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Is chicken supported on 32 bit Linux?
On Tue, May 28, 2013 at 05:04:31PM +0200, Christian Kellermann wrote: * John Long codeb...@inbox.lv [130528 16:48]: On Tue, May 28, 2013 at 04:36:11PM +0200, Christian Kellermann wrote: * John Long codeb...@inbox.lv [130528 16:25]: Hi Christian, Here's the part of the test that crashed. If you need the prior stuff just let me know, I didn't want to post too hugely to the list! Yes, some more info would be nice. Did you just download the 4.8.0.3 tarball untarred it, ran make make install make check? Yes, except I didn't know how to tell the makefile to use -O3 so I changed the C_COMPILER_OPTIMIZATION_OPTIONS after the else in Makefile.linux to match the line before the else. This may indicate a compiler optimisation breaking assumptions in our code. Does it work for you when you leave the values as is? I didn't dream this up, as you know the makefile has provisions for -Os and -O3 so I ASSumed somebody tested that! ;-) It builds fine under -Os, O2, and O3 but the tests fail here at -O2 and -O3. Thanks. /jl ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
[Chicken-users] Chicken 4.8.0 tests segfault on OpenBSD 5.2 AMD64
Hi guys. This is weird because I had no problem building Chicken 4.8.0 on OpenBSD MIPS recently. I am getting a segfault (core dumped) in the make check. It seems to be dying pretty far along in the tests. It's 5,000 lines of output. Do you want to see all of it? Here's a small snipped towards the end: (PASS) (irregex-replace (quote not-an-irx) str) (PASS) (irregex-replace foo foo (lambda (x) (quote not-a-string))) (PASS) (irregex-replace/all (quote not-an-irx) str) (PASS) (irregex-replace/all foo foo (lambda (x) (quote not-a-string))) 1995 tests completed in 0.418 seconds 1995 (100.00%) tests passed 0 (0.00%) tests failed compiler/nursery stress test ... 10 12 20 25 30 35 40 45 50 symbol-GC tests ... ../chicken symbolgc-tests.scm -output-file a.c -verbose -include-path .. gcc a.c -o a.o -c -fno-strict-aliasing -DHAVE_CHICKEN_CONFIG_H -DC_ENABLE_PTABLES -O3 -fomit-frame-pointer -I.. -I/usr/local/include/chicken rm a.c gcc a.o -o a.out -L.. -L/usr/local/lib -Wl,-R/usr/local/lib -lchicken -lm -lpthread ../libchicken.so: warning: strcpy() is almost always misused, please use strlcpy() ../libchicken.so: warning: strcat() is almost always misused, please use strlcat() ../libchicken.so: warning: sprintf() is often misused, please use snprintf() rm a.o Segmentation fault (core dumped) gmake[1]: *** [check] Error 139 gmake[1]: Leaving directory `/tmp/chicken-4.8.0' gmake: *** [check] Error 2 Any idea what could be wrong? Thank you. /jl -- ASCII ribbon campaign ( ) Powered by Lemote Fuloong against HTML e-mail X Loongson MIPS and OpenBSD and proprietary/ \http://www.mutt.org attachments / \ Code Blue or Go Home! Encrypted email preferred PGP Key 2048R/DA65BC04 ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Chicken 4.8.0 tests segfault on OpenBSD 5.2 AMD64
On Wed, Dec 05, 2012 at 12:20:04PM -0500, Mario Domenech Goulart wrote: Hi John, On Wed, 5 Dec 2012 17:23:09 + John Long codeb...@inbox.lv wrote: Hi guys. This is weird because I had no problem building Chicken 4.8.0 on OpenBSD MIPS recently. I am getting a segfault (core dumped) in the make check. It seems to be dying pretty far along in the tests. It's 5,000 lines of output. Do you want to see all of it? Here's a small snipped towards the end: (PASS) (irregex-replace (quote not-an-irx) str) (PASS) (irregex-replace foo foo (lambda (x) (quote not-a-string))) (PASS) (irregex-replace/all (quote not-an-irx) str) (PASS) (irregex-replace/all foo foo (lambda (x) (quote not-a-string))) 1995 tests completed in 0.418 seconds 1995 (100.00%) tests passed 0 (0.00%) tests failed compiler/nursery stress test ... 10 12 20 25 30 35 40 45 50 symbol-GC tests ... ../chicken symbolgc-tests.scm -output-file a.c -verbose -include-path .. gcc a.c -o a.o -c -fno-strict-aliasing -DHAVE_CHICKEN_CONFIG_H -DC_ENABLE_PTABLES -O3 -fomit-frame-pointer -I.. -I/usr/local/include/chicken rm a.c gcc a.o -o a.out -L.. -L/usr/local/lib -Wl,-R/usr/local/lib -lchicken -lm -lpthread ../libchicken.so: warning: strcpy() is almost always misused, please use strlcpy() ../libchicken.so: warning: strcat() is almost always misused, please use strlcat() ../libchicken.so: warning: sprintf() is often misused, please use snprintf() rm a.o Segmentation fault (core dumped) gmake[1]: *** [check] Error 139 gmake[1]: Leaving directory `/tmp/chicken-4.8.0' gmake: *** [check] Error 2 Any idea what could be wrong? Do you always get that error? The symbol-GC test is known to fail sometimes (see http://bugs.call-cc.org/ticket/724) Hi Mario, So far, yes. I ran the build a half dozen times, with and without -O3. It blows at the same spot every time. I'll look at the link you posted tomorrow, thank you. /jl -- ASCII ribbon campaign ( ) Powered by Lemote Fuloong against HTML e-mail X Loongson MIPS and OpenBSD and proprietary/ \http://www.mutt.org attachments / \ Code Blue or Go Home! Encrypted email preferred PGP Key 2048R/DA65BC04 ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Chicken 4.8.0 tests segfault on OpenBSD 5.2 AMD64
On Wed, Dec 05, 2012 at 12:20:04PM -0500, Mario Domenech Goulart wrote: Hi John, On Wed, 5 Dec 2012 17:23:09 + John Long codeb...@inbox.lv wrote: Hi guys. This is weird because I had no problem building Chicken 4.8.0 on OpenBSD MIPS recently. I am getting a segfault (core dumped) in the make check. It seems to be dying pretty far along in the tests. It's 5,000 lines of output. Do you want to see all of it? Here's a small snipped towards the end: (PASS) (irregex-replace (quote not-an-irx) str) (PASS) (irregex-replace foo foo (lambda (x) (quote not-a-string))) (PASS) (irregex-replace/all (quote not-an-irx) str) (PASS) (irregex-replace/all foo foo (lambda (x) (quote not-a-string))) 1995 tests completed in 0.418 seconds 1995 (100.00%) tests passed 0 (0.00%) tests failed compiler/nursery stress test ... 10 12 20 25 30 35 40 45 50 symbol-GC tests ... ../chicken symbolgc-tests.scm -output-file a.c -verbose -include-path .. gcc a.c -o a.o -c -fno-strict-aliasing -DHAVE_CHICKEN_CONFIG_H -DC_ENABLE_PTABLES -O3 -fomit-frame-pointer -I.. -I/usr/local/include/chicken rm a.c gcc a.o -o a.out -L.. -L/usr/local/lib -Wl,-R/usr/local/lib -lchicken -lm -lpthread ../libchicken.so: warning: strcpy() is almost always misused, please use strlcpy() ../libchicken.so: warning: strcat() is almost always misused, please use strlcat() ../libchicken.so: warning: sprintf() is often misused, please use snprintf() rm a.o Segmentation fault (core dumped) gmake[1]: *** [check] Error 139 gmake[1]: Leaving directory `/tmp/chicken-4.8.0' gmake: *** [check] Error 2 Any idea what could be wrong? Do you always get that error? The symbol-GC test is known to fail sometimes (see http://bugs.call-cc.org/ticket/724) That looks pretty similar from 50,000 feet although it seems to me I also got the starting with 1232 symbols and interning 1 symbols messages a few times but in the snippet I sent it appears to have died before that. I can't remember whether I didn't redirect everything in what I sent above but I can reproduce the failure so far 100% of the time (6 times in 6 tries). test environment is OpenBSD AMD64 5.2-stable, chicken 4.8.0 $ gcc -v Reading specs from /usr/lib/gcc-lib/amd64-unknown-openbsd5.2/4.2.1/specs Target: amd64-unknown-openbsd5.2 Configured with: OpenBSD/amd64 system compiler Thread model: posix gcc version 4.2.1 20070719 Thank you. /jl -- ASCII ribbon campaign ( ) Powered by Lemote Fuloong against HTML e-mail X Loongson MIPS and OpenBSD and proprietary/ \http://www.mutt.org attachments / \ Code Blue or Go Home! Encrypted email preferred PGP Key 2048R/DA65BC04 ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Chicken 4.8.0 tests segfault on OpenBSD 5.2 AMD64
On Wed, Dec 05, 2012 at 07:28:18PM +0100, Christian Kellermann wrote: Hi John, * John Long codeb...@inbox.lv [121205 19:16]: On Wed, Dec 05, 2012 at 12:20:04PM -0500, Mario Domenech Goulart wrote: Hi John, On Wed, 5 Dec 2012 17:23:09 + John Long codeb...@inbox.lv wrote: Hi guys. This is weird because I had no problem building Chicken 4.8.0 on OpenBSD MIPS recently. I am getting a segfault (core dumped) in the make check. It seems to be dying pretty far along in the tests. It's 5,000 lines of output. Do you want to see all of it? Here's a small snipped towards the end: This has been happening on and off for me as well as others. The reason for this is currently being debugged by felix and myself which has been stalled by me slacking off for weeks now. Hi Christian, I was surprised because the Loongson build went so flawlessly and all the tests passed. I'm seeing lots of differences in the way OpenBSD runs on these various boxes, not surprisingly. I couldn't build clisp from source on this box at first try either today, although it built fine on the Loongson. Maybe I should abandon these fast boxes and just stay on MIPS! I recommend to ignore it for now as this code path is not taken by default, i.e. garbage collection of weak symbols is *off* by default, so your programs are not at risk. Sorry for the inconveniences. Thanks for the explanation and all the help you've been giving on chicken. I really appreciate it. Good to know and I will go ahead and install it then. /jl Cheers, Christian P.S.: Hopefully the BOSS understandsyour little robot... Went right over my head... -- ASCII ribbon campaign ( ) Powered by Lemote Fuloong against HTML e-mail X Loongson MIPS and OpenBSD and proprietary/ \http://www.mutt.org attachments / \ Code Blue or Go Home! Encrypted email preferred PGP Key 2048R/DA65BC04 ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
[Chicken-users] Is there a Common Lisp like Chicken that compiles to C?
Is there a full-blown CL implementation that compiles to C like Chicken? I'm trying to put together some good language implementations that will work on my OpenBSD MIPS box. /jl -- ASCII ribbon campaign ( ) Powered by Lemote Fuloong against HTML e-mail X Loongson MIPS and OpenBSD and proprietary/ \http://www.mutt.org attachments / \ Code Blue or Go Home! Encrypted email preferred PGP Key 2048R/DA65BC04 ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Is there a Common Lisp like Chicken that compiles to C?
Thanks, I saw that and it looks good at first glance but it's GPL. Anything else worth looking at? On Thu, Nov 22, 2012 at 01:55:20PM +0100, Alex Queiroz wrote: Hallo, On Thu, Nov 22, 2012 at 1:52 PM, John Long codeb...@inbox.lv wrote: Is there a full-blown CL implementation that compiles to C like Chicken? I'm trying to put together some good language implementations that will work on my OpenBSD MIPS box. Maybe ECL will suite you. http://ecls.sourceforge.net/ -- -alex http://www.artisancoder.com/ ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users -- ASCII ribbon campaign ( ) Powered by Lemote Fuloong against HTML e-mail X Loongson MIPS and OpenBSD and proprietary/ \http://www.mutt.org attachments / \ Code Blue or Go Home! Encrypted email preferred PGP Key 2048R/DA65BC04 ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Is there a Common Lisp like Chicken that compiles to C?
Hi John, On Thu, Nov 22, 2012 at 09:16:15AM -0500, John Cowan wrote: John Long scripsit: Thanks, I saw that and it looks good at first glance but it's GPL. Anything else worth looking at? Not really. ECL and GCL are cousins (from the old Kyoto CL code base) and are both GPL. CLiCC is GPL, unmaintained, and supports only a large subset of CLtL1. ThinLisp is Apache, but it's also unmaintained and supports only a subset. Thanks for the info. Unfortunately, ECL apparently won't build on OpenBSD MIPS because of lack of boehm-gc support for MIPS. So that's out for now anyway. The good news is that CMUCL and SBCL (which is a slowly diverging fork of CMUCL), at least according to Weinreb's latest (now last, alas!) survey at http://common-lisp.net/~dlw/LispSurvey.html, have MIPS backends for their native compilers. How well maintained they are I don't know. I was able to build CLISP on my OpenBSD box but I couldn't build SBCL with CLISP. I asked on the SBCL list and they said they require a 32 bit ABI. OpenBSD MIPS uses a 64 bit ABI , so SBCL won't work on my platform either. I'll ask on the CMUCL list. Thank you. /jl -- ASCII ribbon campaign ( ) Powered by Lemote Fuloong against HTML e-mail X Loongson MIPS and OpenBSD and proprietary/ \http://www.mutt.org attachments / \ Code Blue or Go Home! Encrypted email preferred PGP Key 2048R/DA65BC04 ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] How can I check a new build of chicken?
On Mon, Nov 19, 2012 at 09:19:33PM +0100, Felix wrote: From: John Long codeb...@inbox.lv Subject: Re: [Chicken-users] How can I check a new build of chicken? Date: Sun, 18 Nov 2012 14:36:43 + Warning: reference to possibly unbound identifier `values' ../libchicken.so.6.0: warning: strcpy() is almost always misused, please use strlcpy() ../libchicken.so.6.0: warning: strcat() is almost always misused, please use strlcat() ../libchicken.so.6.0: warning: sprintf() is often misused, please use snprintf() Boy, these warnings are annoying. Yeah but can you fix the test case? ;-) ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] How can I check a new build of chicken?
On Tue, Nov 20, 2012 at 08:23:12AM +0200, Timo Myyr?? wrote: Hi, Hi Timo, Test my port on https://github.com/jasperla/openbsd-wip/tree/master/lang/chicken It should be working except for the deployment stuff which is still broken as shown above. Somewhere lurks a reference to the libchicken.so.6 instead of libchicken.so.6.0. Haven't found the cause for it yet. But once it gets fixed I think the port would be ready to be commited to openbsd ports. I don't know what the advantage to scrapping this would be if you are getting the same error as I posted. Your port should be committed against current and the port from current right now is still broken on 5.2. If somebody can fix the tests than the port Christian sent me for 4.7.0 and asked me to update for 4.8.0 (which I did Sunday and yesterday) should be ok. Plus I would like to get the optimizations updated if there's no reason to take the defaults. Thanks. /jl The other thing I noticed is the default is to compile optimized for size in all versions of the port I have seen and also the source build AFAIK. I am not sure why this was chosen. Would it make sense to alter the port to use -O3 or at least -O2? Loongson isn't the fastest thing out there but I can't see using -Os unless it's for an embedded device. Does anyone know why this is? Christian if this is ok do you know how to fix it in the port and also how to fix the tests to copy so.6.0 instead of so.6? /jl -- ASCII ribbon campaign ( ) Powered by Lemote Fuloong against HTML e-mail X Loongson MIPS and OpenBSD and proprietary/ \http://www.mutt.org attachments / \ Code Blue or Go Home! Encrypted email preferred PGP Key 2048R/DA65BC04 ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
[Chicken-users] 4.8.0 status on OpenBSD MIPS
Not hearing anything on the 4.8.0 OpenBSD port discussion, I decided to take Christian's earlier advice and just use the source build. For the record in case anybody else searches the list, the regular Makefile.bsd works fine (as you guys probably already know) on OpenBSD MIPS and all the tests run ok. Because the stock build is so nice and there isn't a whole lot of interest in the port, I'm not going to mess around any further with the port. I'll go with what I have now. Thanks to everybody for making a great Scheme system. /jl -- ASCII ribbon campaign ( ) Powered by Lemote Fuloong against HTML e-mail X Loongson MIPS and OpenBSD and proprietary/ \http://www.mutt.org attachments / \ Code Blue or Go Home! Encrypted email preferred PGP Key 2048R/DA65BC04 ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] How can I check a new build of chicken?
On Fri, Nov 16, 2012 at 10:02:12AM +0100, Christian Kellermann wrote: [text deleted] I am in the middle of trying to get the port updated. It went pretty far and blows up trying to find scheme.import.so which is in the plist but not in the fake build directory. Is this still valid for 4.8.0 or does that library no longer exist? Thanks /jl -- ASCII ribbon campaign ( ) Powered by Lemote Fuloong against HTML e-mail X Loongson MIPS and OpenBSD and proprietary/ \http://www.mutt.org attachments / \ Code Blue or Go Home! Encrypted email preferred PGP Key 2048R/DA65BC04 ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] How can I check a new build of chicken?
On Sun, Nov 18, 2012 at 03:20:52PM +0100, Felix wrote: I am in the middle of trying to get the port updated. It went pretty far and blows up trying to find scheme.import.so which is in the plist but not in the fake build directory. Is this still valid for 4.8.0 or does that library no longer exist? It has been removed and is integrated into the core module system. cheers, felix Thank you. In the meantime I looked at my 4.8.0 source build and realized it wasn't there so I have been moving on. The port builds and installs fine. The test suite runs for a long time and finally errors out. This is just stderr. If you need the whole thing let me know and I'll capture it and repost. I always forget how to grab stdout and stderr from ksh redirection and have to look it up. Note: global variable `bla#blabla' is only locally visible and never used Note: global variable `foo#bar' is only locally visible and never used ../libchicken.so.6.0: warning: strcpy() is almost always misused, please use strlcpy() ../libchicken.so.6.0: warning: strcat() is almost always misused, please use strlcat() ../libchicken.so.6.0: warning: sprintf() is often misused, please use snprintf() ../libchicken.so.6.0: warning: strcpy() is almost always misused, please use strlcpy() ../libchicken.so.6.0: warning: strcat() is almost always misused, please use strlcat() ../libchicken.so.6.0: warning: sprintf() is often misused, please use snprintf() ../libchicken.so.6.0: warning: strcpy() is almost always misused, please use strlcpy() ../libchicken.so.6.0: warning: strcat() is almost always misused, please use strlcat() ../libchicken.so.6.0: warning: sprintf() is often misused, please use snprintf() ../libchicken.so.6.0: warning: strcpy() is almost always misused, please use strlcpy() ../libchicken.so.6.0: warning: strcat() is almost always misused, please use strlcat() ../libchicken.so.6.0: warning: sprintf() is often misused, please use snprintf() ../libchicken.so.6.0: warning: strcpy() is almost always misused, please use strlcpy() ../libchicken.so.6.0: warning: strcat() is almost always misused, please use strlcat() ../libchicken.so.6.0: warning: sprintf() is often misused, please use snprintf() Note: global variable `foo#spec' is only locally visible and never used ../libchicken.so.6.0: warning: strcpy() is almost always misused, please use strlcpy() ../libchicken.so.6.0: warning: strcat() is almost always misused, please use strlcat() ../libchicken.so.6.0: warning: sprintf() is often misused, please use snprintf() ../libchicken.so.6.0: warning: strcpy() is almost always misused, please use strlcpy() ../libchicken.so.6.0: warning: strcat() is almost always misused, please use strlcat() ../libchicken.so.6.0: warning: sprintf() is often misused, please use snprintf() ../libchicken.so.6.0: warning: strcpy() is almost always misused, please use strlcpy() ../libchicken.so.6.0: warning: strcat() is almost always misused, please use strlcat() ../libchicken.so.6.0: warning: sprintf() is often misused, please use snprintf() ../libchicken.so.6.0: warning: strcpy() is almost always misused, please use strlcpy() ../libchicken.so.6.0: warning: strcat() is almost always misused, please use strlcat() ../libchicken.so.6.0: warning: sprintf() is often misused, please use snprintf() 0m14.19s real 0m13.88s user 0m0.10s system 0m5.55s real 0m5.39s user 0m0.05s system ../libchicken.so.6.0: warning: strcpy() is almost always misused, please use strlcpy() ../libchicken.so.6.0: warning: strcat() is almost always misused, please use strlcat() ../libchicken.so.6.0: warning: sprintf() is often misused, please use snprintf() [panic] callback returned twice - execution terminated callback-tests.scm:16: print g67 callback-tests.scm:17: ##sys#gc callback-tests.scm:17: g11 callback-tests.scm:7: call/cc callback-tests.scm:9: print callback-tests.scm:19: command-line-arguments callback-tests.scm:20: k1 callback-tests.scm:9: print -- ../libchicken.so.6.0: warning: strcpy() is almost always misused, please use strlcpy() ../libchicken.so.6.0: warning: strcat() is almost always misused, please use strlcat() ../libchicken.so.6.0: warning: sprintf() is often misused, please use snprintf() [GC] level 1 gcs(minor) 1 gcs(major) 1 [GC] stack 0x7fed8578 0x7ff561c8 0x7ffd8578 [GC] from 0x5a79 0x5a7c6058 0x5a81 0x00036058 [GC]to 0x504d8000 0x504d8000 0x50558000 [GC] 0 locatives (from 32) [GC] level 1 gcs(minor) 1 gcs(major) 2 [GC] stack 0x7fed8578 0x7ffd7558 0x7ffd8578 [GC] from 0x504d8000 0x5050e058 0x50558000 0x00036058 [GC]to 0x5a79 0x5a79 0x5a81 [GC] 0 locatives (from 32) [GC] (old) fromspace:
Re: [Chicken-users] How can I check a new build of chicken?
On Fri, Nov 16, 2012 at 10:02:12AM +0100, Christian Kellermann wrote: * John Long codeb...@inbox.lv [121116 09:59]: On Fri, Nov 16, 2012 at 08:42:29AM +0100, Christian Kellermann wrote: * John Long codeb...@inbox.lv [121116 06:18]: On Thu, Nov 15, 2012 at 07:18:13PM +0100, Christian Kellermann wrote: For what it's worth here's my Chicken 4.7.0 port for OpenBSD. zmyrgel's work supercedes this I think. http://pestilenz.org/~ckeen/chicken.tgz Christian thank you! This builds fine on 5.2 and csc builds the foo.scm program fine. I did notice libchicken is not linked with libffi though. Is this needed for anything? Current chicken does not use libffi, if that requirement is still in there then it's a bug. No problem, good to know. I saw it in 2.6 and didn't know whether it should be in later builds. There is no requirement, just a misunderstanding on my part. Sorry for the false alarm. What you can do is to just crank up the chicken version in the port Makefile to 4.8.0. I think it should still work fine and you will get an uptodate chicken. Could you try this? Yes, sure. The only thing is the checksums/hashes will break and I think that will stop the port from building. I need to figure out those are generated unless you know offhand. make makesum make update-plist (or however that is spelled, see the man page) Thanks. I'll try this over the weekend and let you know asap! /jl -- ASCII ribbon campaign ( ) Powered by Lemote Fuloong against HTML e-mail X Loongson MIPS and OpenBSD and proprietary/ \http://www.mutt.org attachments / \ Code Blue or Go Home! Encrypted email preferred PGP Key 2048R/DA65BC04 ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
[Chicken-users] How can I check a new build of chicken?
Hi, I just spent a couple days attempting to get chicken installed on OpenBSD MIPS. I am new to scheme and chicken sounds fantastic from what I read because it compiles to C, which is just what I need on a weird platform like MIPS. I tried the test program in the doc with csc and it broke because of the unresolved references to pthread entry points. This is not your problem, please bear with me and I will explain what I am trying to do. OpenBSD has a build system and on the current release (5.2) there is a problem in the build for chicken (2.6) in that libchicken does not get linked with libpthread. I know this is the issue because I can build it on OpenBSD current and libchicken has libpthread linked and I don't get the error. I am not familiar with UNIX or OpenBSD's builds enough to fix it right so I monkeyed around with some of the builds Makefile settings and it finally works. Surprisingly (and so you don't bring out the cluebat) I even tried the build that works on OpenBSD current on the 5.2 release version and the identical build doesn't work on 5.2. There are a lot of changes in current and I don't know enough to track down what's going on. The build does finish cleanly with my minor changes and the foo.scm does get built and run fine with csc. I realize this is an odd question since you do provide a test suite with the source tarball, but given I installed this through a build system and didn't get to use the original makefile you supply, other than running csc on the tiny foo.scm example in the chicken doc, how can I verify that what I have installed is correct? Is there some way to run your test suite now? I want to make sure this is built right so I don't run into problems later when I use more advanced features. Thanks for the help. /jl -- ASCII ribbon campaign ( ) Powered by Lemote Fuloong against HTML e-mail X Loongson MIPS and OpenBSD and proprietary/ \http://www.mutt.org attachments / \ Code Blue or Go Home! Encrypted email preferred PGP Key 2048R/DA65BC04 ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] How can I check a new build of chicken?
Hey Christian, On Thu, Nov 15, 2012 at 06:18:43PM +0100, Christian Kellermann wrote: That version is way outdated. There is a more recent chicken port in the WIP ports git tree. Regardless of that chicken builds just fine on the loongson. I am running it there myself. Oh cool, another loongson owner! What OS are you running? Just grab the latest release tarball and build that one. The current version is 4.8.0. I did actually start doing that and then I thought it would be better to try getting the OpenBSD build to work because it keeps all the dependencies updated. Is there a way to check the install I have now, given the comments in the chicken makefile seem to suggest you have to do the test with the same parms as the build (and I'm not exactly sure what happened there)? If so, I'd prefer that at this point since I'm new to scheme and probably won't miss the new features for a while yet. If there is no way to run the test suite, then I'll start my 4.8.0 build again and use that instead. Thanks for getting back to me so quickly! /jl ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] How can I check a new build of chicken?
On Thu, Nov 15, 2012 at 07:10:51PM +0100, Christian Kellermann wrote: * John Long codeb...@inbox.lv [121115 19:03]: Hey Christian, On Thu, Nov 15, 2012 at 06:18:43PM +0100, Christian Kellermann wrote: That version is way outdated. There is a more recent chicken port in the WIP ports git tree. Regardless of that chicken builds just fine on the loongson. I am running it there myself. Oh cool, another loongson owner! What OS are you running? OpenBSD of course :) Awesome! How about patching the port for 5.2 to use 4.8.0 and pthreads? ;-) Well the chicken core itself has GCC and gmake as a dependency. The extensions are not tracked by either port. So you wouldn't gain much. It also has libpthread, libc (okay) libffi, and libm if I am reading things right. Those are the ones I was more worried about. gcc doesn't change much, as you know. But there are about two dozen autoconfs and gmakes. Also note that in order to run make check you will need to install chicken first, as there are some tests that require the runtime and other things to be in place. My modified port did build and install in /usr/local. But after the port builds I don't know if the normal chicken build tree exists. That's why I didn't know if I could run the normal tests after that. Can you think of an easy way, given chicken is already installed in /usr/local? Or should I just bag it and go on? If you are afraid of that you can choose a PREFIX in /tmp or somewhere convenient. Just make sure that the PREFIX matches on each invocatoin of make. Also see the README on details. Are you saying this about the 4.8 build? I'm not worried about that since I build everything from source on Linux without a package manager or ports system (Slackware). On OpenBSD I try to play by the rules because I know I'll get no help if I deviate ;-) You can save yourself most pains if you start from the WIP: https://github.com/jasperla/openbsd-wip/tree/master/lang/chicken Thanks for getting back to me so quickly! No problem, I do hope you get started quickly! Kind regards, Christian Thanks a lot Christian. /jl ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] How can I check a new build of chicken?
On Thu, Nov 15, 2012 at 07:18:13PM +0100, Christian Kellermann wrote: For what it's worth here's my Chicken 4.7.0 port for OpenBSD. zmyrgel's work supercedes this I think. http://pestilenz.org/~ckeen/chicken.tgz Thanks, I'll try this now and get back to you tomorrow. /jl ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] How can I check a new build of chicken?
On Thu, Nov 15, 2012 at 07:18:13PM +0100, Christian Kellermann wrote: For what it's worth here's my Chicken 4.7.0 port for OpenBSD. zmyrgel's work supercedes this I think. http://pestilenz.org/~ckeen/chicken.tgz Christian thank you! This builds fine on 5.2 and csc builds the foo.scm program fine. I did notice libchicken is not linked with libffi though. Is this needed for anything? /jl -- ASCII ribbon campaign ( ) Powered by Lemote Fuloong against HTML e-mail X Loongson MIPS and OpenBSD and proprietary/ \http://www.mutt.org attachments / \ Code Blue or Go Home! Encrypted email preferred PGP Key 2048R/DA65BC04 ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] How can I check a new build of chicken?
On Thu, Nov 15, 2012 at 12:01:03PM -0700, .alyn.post. wrote: Both Christian and I run Chicken Scheme on OpenBSD. There may well be others, but the OpenBSD platform is well supported by Chicken and does see regular use. I suspect you can expect help here if you decide to run Chicken core/latest version by compiling from source. Hi Alan, Excellent, glad to see people using OpenBSD and Chicken Scheme together! Looking over the chicken doc you guys have an amazing system here! /jl -- ASCII ribbon campaign ( ) Powered by Lemote Fuloong against HTML e-mail X Loongson MIPS and OpenBSD and proprietary/ \http://www.mutt.org attachments / \ Code Blue or Go Home! Encrypted email preferred PGP Key 2048R/DA65BC04 ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
