[Aldor-l] Testing the 32bit libraries on a 64bit system

[Christian Aistleitner]

Hello,

recently, I found the following text in my mailbox:

> (1) I recently tried unsuccessfully to install aldor on an amd64 machine
> running suse linux 9.2 64 bit. I recall your email with three different
> methods on how to do this, etc.
>
> I want to use the method employing the 32 bit gcc libraries which I  
> think are
> installed on my system (dont know how to verify this). Please email me  
> some
> instructions on how to use these libraries to compile and install aldor  
> on
> the above-mentioned system.

As this possible applies to several other users, I am answering on this  
list:

Aldor is shipped with 32bit libraries.
In the end, Aldor uses (not necessarily, but typically) gcc to compile  
code.
On 64bit systems, gcc (not necessarily, but typically) compiles to 64bit  
code.

32bit and 64bit cannot be linked together.

As there is no way to obtain all Aldor libraries in a 64bit version, gcc  
has to be told to produce 32bit binaries.

I have never worked on suse 9.2. But generally, gcc is told to compile to  
32bit by the switch -m32.

Consider the attached file test.as.

In a 32bit environment it is compiled to an executable by
aldor -Fx -laldor test.as
. In a 64bit environment,
aldor -C args=-Wopts=-m32 -Fx -laldor test.as
compiles it to an 32 bit executable (The additional parameter tells unicl  
to pass -m32 to gcc).

For any call to aldor, add the parameter
-C args=-Wopts=-m32
. As this is cumbersome, $ALDORROOT/include/aldor.conf can be adjusted to  
pass -m32 to gcc automatically.


--
Best regards,
Christian

-------------- next part --------------
A non-text attachment was scrubbed...
Name: test.as
Type: application/octet-stream
Size: 74 bytes
Desc: not available
URL: <http://mail.aldor.org/pipermail/aldor-l_aldor.org/attachments/20051005/04224822/attachment-0001.obj>