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
Re: [Chicken-users] How can I check a new build of chicken?
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. cheers, felix ___ 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. It's hard to understand that people can live with them. Cheers, Peter -- http://sjamaan.ath.cx -- The process of preparing programs for a digital computer is especially attractive, not only because it can be economically and scientifically rewarding, but also because it can be an aesthetic experience much like composing poetry or music. -- Donald Knuth ___ 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. cheers, felix I suspect the OpenBSD team would say Well, stop using these routines. Because if you're going to put such a message in your linker you're also going to be annoying in person. I'm not recompiling my linker enough to make it worth it, but the patch to remove this check is ~5 lines. It's a pitty there isn't an environmental variable or something to shut them up. -Alan -- .i ma'a lo bradi cu penmi gi'e du ___ 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?
* 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) Cheers, Christian -- In the world, there is nothing more submissive and weak than water. Yet for attacking that which is hard and strong, nothing can surpass it. --- Lao Tzu ___ 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: * 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
Re: [Chicken-users] How can I check a new build of chicken?
Hi John, * John Long codeb...@inbox.lv [121115 18:14]: 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. 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. Just grab the latest release tarball and build that one. The current version is 4.8.0. Tarballs can be found at http://code.call-cc.org HTH, Christian -- In the world, there is nothing more submissive and weak than water. Yet for attacking that which is hard and strong, nothing can surpass it. --- Lao Tzu ___ 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?
* 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 :) 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. 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. 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. 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. 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 -- In the world, there is nothing more submissive and weak than water. Yet for attacking that which is hard and strong, nothing can surpass it. --- Lao Tzu ___ 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?
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 Kind regards, Christian -- In the world, there is nothing more submissive and weak than water. Yet for attacking that which is hard and strong, nothing can surpass it. --- Lao Tzu ___ 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
Re: [Chicken-users] How can I check a new build of chicken?
* 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. 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? Kind regards, Christian -- In the world, there is nothing more submissive and weak than water. Yet for attacking that which is hard and strong, nothing can surpass it. --- Lao Tzu ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
