[Aldor-l] gcc bitness and version (was: Re: [Axiom-developer] Spad and its object model)

[Christian Aistleitner]

Hello,

>> I got
>> http://wiki.axiom-developer.org/public/aldor-linux-x86_64-v1.0.2.bin
>> and so far it works fine from with in axiom (debian etch amd64).
>> Is this a true 64bit version?

If the file hasn't been changed recently, then it is a 64bit version.
If you did not tamper with it's config files, it should give you proper  
64bit executables--provided you use a suitable C compiler (e.g.: gcc <4.0).

However, note that it is not an official build from aldor.org.
Furthermore, note that the current "stable" Aldor compiler version is  
1.0.3.

But in the end of the day, the file you downloaded is the only 64bit Aldor  
compiler I know about.

>> however with your instructions I get
>>> aldor -laldor -fo -fao aaa.as
>> cc1: error: unrecognized command line option "-fwritable-strings"
>> #1 (Fatal Error) C compile failed.  Command was: unicl
>> -I/usr/opt/AxiomAldor-1.0.2/aldor/linux/1.0.2/include -c aaa.c
>> #1 (Warning) Removing file `aaa.c'.
>>
>> Is this one of the errors
>> http://www.aldor.org/pipermail/aldor-l/2005-June/000074.html
>> talks about?

Actually its non of the potential problems of the cited post.
Aldor officially only supports 32bit systems with gcc <4.0.
You seem to be using Aldor on a 64bit system with gcc>=4.0.

The cited post addresses 32 vs. 64 bits.
As Ralf already said, your problem is gcc <4.0 vs. gcc >=4.0.

> I think it is rather a problem with gcc 4.0. To be more precise: The
> C-code produced by the Aldor compiler must be compiled with gcc 3.3 or
> so. gcc4.0 does not work.

IIRC gcc3.4 should work as well. But you might get a deprecation warning  
about "-fwritable-strings".
With gcc 4.0, writable strings support has finally been removed from gcc.  
Aldor still uses them. So it just won't work out.

Kind regards,
Christian