[Chicken-users] bind error : "bad prototype syntax"
For the attached scheme file I'm getting the error below. The line it's complaining about looks like this: extern CL_API_ENTRY cl_int CL_API_CALL clGetDeviceIDs( cl_platform_id , cl_device_type , cl_uint , cl_device_id * , cl_uint * ) CL_API_SUFFIX__VERSION_1_0; cl_int and CL_API_CALL are in cl_platform.h which is included in cl.h. Putting #include #include in cl.scm results in the same error also. Thanks again, -Dave $ csc -s -o cl.so cl.scm -framework OpenCL -framework Accelerate -vv /usr/local/bin/chicken-4.6.0 cl.scm -output-file cl.c -dynamic -feature chicken-compile-shared -verbose Loading compiler extensions... debugging info: calltrace loading identifier database /usr/local/lib/chicken/5/modules.db ... compiling `cl.scm' ... pass: source ; loading /usr/local/lib/chicken/5/bind.import.so ... ; loading /usr/local/lib/chicken/5/scheme.import.so ... ; loading /usr/local/lib/chicken/5/chicken.import.so ... ; loading /usr/local/lib/chicken/5/foreign.import.so ... ; loading /usr/local/lib/chicken/5/bind-translator.so ... ; loading /usr/local/lib/chicken/5/silex.so ... ; loading /usr/local/lib/chicken/5/matchable.so ... Error: during expansion of (bind19 ...) - bad prototype syntax: ((id "cl_int") (id "CL_API_CALL") (id "clGetDeviceIDs") open-paren (id "cl_platform_id") comma (id "cl_device_type") comma (id "cl_uint") comma (id "cl_device_id") star comma (id "cl_uint") star close-paren (id "CL_API_SUFFIX__VERSION_1_0")) Call history: (##core#module cl #t (import scheme chicken bind) (bind* "\n#include \n\n___declare(exp... (import scheme chicken bind) (##core#undefined) (bind* "\n#include \n\n___declare(export_constants , yes)\n\n#define CL_TRUE ... (##core#begin (declare18 (foreign-declare "\n#include \n\n___declare(export_constants ,... (declare18 (foreign-declare "\n#include \n\n___declare(export_constants , yes)\n\n#defi... (##core#declare (foreign-declare "\n#include \n\n___declare(export_constants , yes)\n\n... (##core#begin (##core#undefined)) (##core#undefined) (bind19 "\n#include \n\n___declare(export_constants , yes)\n\n#define CL_TRUE ...<-- Error: shell command terminated with non-zero exit status 17920: /usr/local/bin/chicken-4.6.0 cl.scm -output-file cl.c -dynamic -feature chicken-compile-shared -verbose cl.scm Description: Binary data ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] chicken script with many CLI arguments
From: Sven Hartrumpf Subject: [Chicken-users] chicken script with many CLI arguments Date: Wed, 08 Dec 2010 13:15:32 +0100 (CET) > Wed, 08 Dec 2010 05:37:28 -0500 (EST), felix wrote: >> Can you try the "experimental" branch? I checked in a change >> that hopefully improves the situation. > > Yes, works perfectly. > > Thanks, Felix! You're welcome. cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
[Chicken-users] chicken script with many CLI arguments
Wed, 08 Dec 2010 05:37:28 -0500 (EST), felix wrote: > Can you try the "experimental" branch? I checked in a change > that hopefully improves the situation. Yes, works perfectly. Thanks, Felix! ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] EOF problem
From: Peter Bex Subject: Re: [Chicken-users] EOF problem Date: Tue, 7 Dec 2010 22:30:27 +0100 > On Tue, Dec 07, 2010 at 04:18:49PM -0500, David Dreisigmeyer wrote: >> Thank you Alan and Peter - that took care of it. >> >> csc is also complaining about, e.g., int32_t , uint , uint64_t , >> __attribute__ and >> >> #define CL_API_SUFFIX__VERSION_1_0 >> AVAILABLE_MAC_OS_X_VERSION_10_6_AND_LATER > > The problem with int32_t and such might be caused by the fact you don't > have the #include in the foreign-parse block so it doesn't see the > definitions in order to be able to convert the int32_t to its real type. > > About __attribute__: perhaps the easyffi egg's C parser can't handle that? > No, I don't think so. And bind neither, but I can look into that at some stage. cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] chicken script with many CLI arguments
From: Sven Hartrumpf Subject: [Chicken-users] chicken script with many CLI arguments Date: Tue, 07 Dec 2010 14:43:10 +0100 (CET) > Hi all. > > I am trying to call a chicken script with many command line > arguments (over 1 file names). > Can you try the "experimental" branch? I checked in a change that hopefully improves the situation. cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] question about commit c157ff502829c6f2856df4a963d81a88ee241ebf
From: Alan Post Subject: [Chicken-users] question about commit c157ff502829c6f2856df4a963d81a88ee241ebf Date: Tue, 7 Dec 2010 09:05:16 -0700 > I have a question about commit > c157ff502829c6f2856df4a963d81a88ee241ebf, the change for detecting > cycles in equal? > > The last change in runtime.c is as follows: > > > @@ -3865,7 +3876,8 @@ C_regparm C_word C_fcall C_equalp(C_word x, C_word y) >C_header header; >C_word bits, n, i; > > - C_stack_check; > + if(C_stack_test) > +barf(C_CIRCULAR_DATA_ERROR, "equal?"); > > loop: >if(x == y) return 1; > > Given that equal? returns either #t or #f, is it the case here that > *if* we have detected circular data, is it by definition eq? to > itself, and therefor rather than calling barf() here we can return > 1? No, because two compared data-structures might be circular, yet not made up of identical data. > > If that isn't true, could we perform this check later in this > routine, say before we recurse rather than immediately upon > entering? That would allow some non-recursive checks to run (and > potentially succeed) before deciding that we really have to > terminate. I think we could detect some cases of equality that this > patch won't, because of the placement of this check. > > It seems that the stack check is placed in a "generic" location that > would work with any potentially circular data, but in the case of > equal?, the fact that it returns a boolean value means we can do > better than "generic" code that might return any value. Sorry, I'm not sure I understand - could you show an example of such a case? cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] url links for images in wiki
* Peter Lane [101208 01:10]: > Hi, > > It seems I wrote too soon about getting images showing in the wiki. The URL > is correct, but, when trying from another computer, I am asked to enter the > repository password to see the images. > > Is there any way around this? Adding the anonymous user in the URL? Cheers, Christian ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
