[Aldor-l] Compiling setup

[PCR]

Page, Bill wrote:
> On Thursday, August 10, 2006 6:39 PM PCR wrote:
>   
>> I was trying a first problem in Aldor, and got this result.
>> Mayhap I set things up wrong?  Thanks for any help.
>>
>> pcr1 at Delta:~/aldor$ aldor -fx -laldor sieve.as
>> cc1: error: unrecognized command line option "-fwritable-strings"
>> #1 (Fatal Error) C compile failed.  Command was: unicl 
>> -I/usr/local/aldor/linux/1.0.3/include -c sieve.c
>> #1 (Warning) Removing file `sieve.c'
>>
>>     
>
> You don't say what computer and version of operating
> system you are using (you should in any error report or
> request for help), but the problem seems to be that you
> are using a version of the gcc C compiler that is "too new".
>
> The -fx option tells Aldor to compile a native C runtime
> program but the curent version of the Aldor compiler
> generated intermediate C code that will only work with
> a C compiler that supports "writable strings". Newer
> versions of C (since gcc 4.0) do not support modification
> of string constants.
>
> You can revert to an earlier version of C.
>
> It is also possible to get around this limitation by
> compiling to intermediate lisp and then using a lisp
> compiler such as GCL that works with the newer C compilers.
>
> Regards,
> Bill Page.
>
>
>   
I am trying the detour. aldor -flsp -laldor sieve.as gave me a file 
sieve.lsp. Running gcl and typing (load "sieve.lsp") at the promt gave me:

 >(load "sieve.lsp")

Loading sieve.lsp

Error: "FOAM" is not of type (OR SYMBOL STRING ...).
Fast links are on: do (si::use-fast-links nil) for debugging
Error signalled by IN-PACKAGE.
Broken at IN-PACKAGE. Type :H for Help.
 >>

This has to be my mistake somehow!