Jim & Toby: thanks for your help. My system doesn't seem to recognize the
csi command:

$ csi -s test.scm
> -bash: csi: command not found
>

"csc -help" returns the same message.

Seems like something needs to be added to the path for bash to pick it up?

Cheers,
James


On Wed, Feb 15, 2012 at 7:19 PM, Jim Ursetto <[email protected]> wrote:

> OK, I need to update the docs to say the workaround is needed on 10.7 as
> well then.  Thanks.
>
> Use 'csi -script myfile.scm' to run a .scm file at the command line, or
> 'csi' to enter the interpreter.
>
> On Feb 15, 2012, at 11:16 AM, James Abbott wrote:
>
> Hi Jim,-
>
> running:
>
>
>> make PLATFORM=macosx C_COMPILER=gcc-4.2 PLATFORM=macosx ARCH=x86-64
>>
>
> built the source. Output of uname -a:
>
>
>> Darwin james-abbotts-macbook.local 11.3.0 Darwin Kernel Version 11.3.0:
>> Thu Jan 12 18:48:32 PST 2012; root:xnu-1699.24.23~1/RELEASE_I386 i386
>>
>
> Now, is there a command-line tool for running Scheme files that comes with
> Chicken? Ie, can I run something like:
>
> scheme myfile.scm
> chicken myfile.scm
> bok myfile.scm
>
> ?
>
> Thanks,
> James
>
>
> On Wed, Feb 15, 2012 at 4:21 PM, Jim Ursetto <[email protected]> wrote:
>
>> Ok, then also add ARCH=x86-64 like you had originally.  It was my
>> understand this wasn't needed on 10.6 or 10.7 and I thought I confirmed
>> that, but maybe not.  Let me know if it works, and if so, what the output
>> of `uname -a` on your system is.
>>
>> On Feb 15, 2012, at 2:49 AM, James Abbott wrote:
>>
>> Hi all,-
>>
>> thanks for the replies. I have Xcode 4.1. So the "make PLATFORM=macosx
>> C_COMPILER=gcc-4.2" command should work. However I get this message:
>>
>> make -f ./Makefile.macosx CONFIG= all
>>> gcc-4.2  -c apply-hack.x86.S -o apply-hack.x86.o
>>> apply-hack.x86.S:35:suffix or operands invalid for `call'
>>> make[1]: *** [apply-hack.x86.o] Error 1
>>> make: *** [all] Error 2
>>>
>>
>> Here's what gcc -v returned:
>>
>> Using built-in specs.
>>> Target: i686-apple-darwin11
>>> Configured with:
>>> /private/var/tmp/llvmgcc42/llvmgcc42-2335.15~25/src/configure
>>> --disable-checking --enable-werror --prefix=/Developer/usr/llvm-gcc-4.2
>>> --mandir=/share/man --enable-languages=c,objc,c++,obj-c++
>>> --program-prefix=llvm- --program-transform-name=/^[cg][^.-]*$/s/$/-4.2/
>>> --with-slibdir=/usr/lib --build=i686-apple-darwin11
>>> --enable-llvm=/private/var/tmp/llvmgcc42/llvmgcc42-2335.15~25/dst-llvmCore/Developer/usr/local
>>> --program-prefix=i686-apple-darwin11- --host=x86_64-apple-darwin11
>>> --target=i686-apple-darwin11 --with-gxx-include-dir=/usr/include/c++/4.2.1
>>> Thread model: posix
>>> gcc version 4.2.1 (Based on Apple Inc. build 5658) (LLVM build
>>> 2335.15.00)
>>>
>>
>>
>> Seems like I'll need to build from git anyway!
>>
>> Cheers,
>> James
>>
>>
>>
>> On Wed, Feb 15, 2012 at 5:16 AM, Jim Ursetto <[email protected]>wrote:
>>
>>> Check out the latest code, apply the ticket patches, make a boot
>>> chicken, then build chicken with the chicken-boot binary. Normal procedure
>>> in other words when building from git.
>>>
>>>
>>> On Feb 14, 2012, at 19:23, Stephen Eilert <[email protected]> wrote:
>>>
>>>
>>> On Tue, Feb 14, 2012 at 12:28 PM, Jim Ursetto <[email protected]>wrote:
>>>
>>>> On Feb 14, 2012, at 9:26 AM, Jim Ursetto wrote:
>>>>
>>>> > This works with XCode 4.2 on Lion.  If this works without hanging,
>>>> you're done.
>>>> > If you have already upgraded to XCode 4.3...
>>>>
>>>> Oops.  I meant it works until XCode 4.2, and if you upgraded to XCode
>>>> 4.2 already (which you probably have) then you have to follow the other
>>>> alternate instructions.  Even I am confused.
>>>> Jim
>>>
>>>
>>> So, in case one has upgraded to XCode 4.3 already and doesn't have a
>>> chicken binary anymore...
>>>
>>>
>>>
>>> -- Stephen
>>>
>>> *"Kids these days.*
>>> *Whatever happened to hard work?"*
>>>
>>>        -- Joel Spolsky, The perils of javaschools
>>>
>>>
>>>
>>
>>
>
>
_______________________________________________
Chicken-users mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/chicken-users

Reply via email to