Building TCL 8.4.13 on 64bit SuSE

[Jay Rohr]

I'm tring to build TCL 8.4.13 on a AMD 64 bit SuSE 10.0 dist.

uname -a
--> Linux nas2 2.6.13-15.8-smp #1 SMP Tue Feb 7 11:07:24 UTC 2006 x86_64 x86_64 x86_64 GNU/Linux

gcc --version
--> gcc (GCC) 4.0.2 20050901

./configure --enable-64bit give the following message
configure: warning: 64bit support being disabled -- don't know magic for this platform

Anyone know the magic ? :-)

[Don Porter]

In article <oGgug.4073$Ss2.1102@trnddc01>, Jay Rohr wrote:
> ./configure --enable-64bit give the following message
> configure: warning: 64bit support being disabled -- don't know magic for this platform
>
> Anyone know the magic ? :-)

Try just a plain configure without the --enable-64bit option and
see whether you get 64-bit binaries.

If I'm not mistaken, the option looks like "--enable-64bit" but
really means "--enable-64-bit-on-some-Solaris-and-SGI-boxen".

--
| Don Porter Mathematical and Computational Sciences Division |
| donald...@nist.gov Information Technology Laboratory |
| http://math.nist.gov/~DPorter/ NIST |
|______________________________________________________________________|

[Shaun Deacon]

I also had this issue on 64-bit RedHat Enterprise.

As Don mentions, gcc should compile OK without specifying
--enable-64bit. However, you may still get the above warning
message - I ignored this and the resulting compilation was
still OK...

The following thread gives some more background :

http://groups.google.com/group/comp.lang.tcl/browse_frm/thread/8375ee4c57c91666

hth
Shaun

[Matthias Kraft]

Don Porter wrote:
> In article <oGgug.4073$Ss2.1102@trnddc01>, Jay Rohr wrote:
>> ./configure --enable-64bit give the following message
>> configure: warning: 64bit support being disabled -- don't know magic for this platform
>>
>> Anyone know the magic ? :-)
>
> Try just a plain configure without the --enable-64bit option and
> see whether you get 64-bit binaries.
>
> If I'm not mistaken, the option looks like "--enable-64bit" but
> really means "--enable-64-bit-on-some-Solaris-and-SGI-boxen".

Well I thought that was what the switch --enable-64bit-vis is for.

tcl.m4 contains quite a lot of code to determine what to do if 64bit
compiles are requested on the various systems. Well at least for AIX,
HP-UX, some IRIX, Darwin and Solaris.

It's missing the code for Linux, though.

To work around this, one should define CC with the appropriate flags:
CC="gcc -m32" to ensure 32bit results (-m31 for Linux/s390) and
CC="gcc -m64" for 64bit results respectively. This seems to work
reliably.

kind regards
--
Matthias Kraft
Software AG, Germany

(They that can give up essential liberty to obtain a little temporary)
(safety deserve neither liberty nor safety. -- Benjamin Franklin)

[Jay Rohr]

Matthias Kraft wrote:
> Don Porter wrote:
>
>>In article <oGgug.4073$Ss2.1102@trnddc01>, Jay Rohr wrote:
>>
>>>./configure --enable-64bit give the following message
>>>configure: warning: 64bit support being disabled -- don't know magic for this platform
>>>
>>>Anyone know the magic ? :-)
>>
>>Try just a plain configure without the --enable-64bit option and
>>see whether you get 64-bit binaries.
>>
>>If I'm not mistaken, the option looks like "--enable-64bit" but
>>really means "--enable-64-bit-on-some-Solaris-and-SGI-boxen".
>
>
> Well I thought that was what the switch --enable-64bit-vis is for.
>
> tcl.m4 contains quite a lot of code to determine what to do if 64bit
> compiles are requested on the various systems. Well at least for AIX,
> HP-UX, some IRIX, Darwin and Solaris.
>
> It's missing the code for Linux, though.
>
> To work around this, one should define CC with the appropriate flags:
> CC="gcc -m32" to ensure 32bit results (-m31 for Linux/s390) and
> CC="gcc -m64" for 64bit results respectively. This seems to work
> reliably.
>
> kind regards

Don's suggestion was right on. Leaving the --enable-64bit switch off
completely resulted in a 64bit executable and libs with no complaints.

However, specifing --disable-64bit resulted in 32 bit executables.