Tcl Source Code

View Ticket
Login
Ticket UUID: 1c4ba6fa409870b5b78c784be6949f2905c937e2
Title: --enable-64bit and Linux aarch64
Type: Bug Created on: 2020-11-12 07:57:08
Submitter: chrstphrchvz Assigned to: nobody
Subsystem: 53. Configuration and Build Tools Severity: Cosmetic
Priority: 5 Medium Last modified: 2026-10-20 12:10:59
Status: Open Closed by: nobody
Resolution: None Closed on:
Version: 9.1.0
Description:

Using Debian 10 aarch64 (Raspberry Pi 3B), i.e. 64-bit ARM rather than 32-bit. The configure script does not seem to detect it as a 64-bit platform, and explicitly requesting 64-bit support with --enable-64bit causes a warning:

checking if compiler accepts -m64 flag... no
configure: WARNING: 64bit support being disabled -- don't know magic for this platform

(-m64 does not appear to be a valid GCC flag on aarch64.)

It is not clear to me what enabling/disabling 64-bit support actually does, or whether I should even be requesting 64-bit support on aarch64. I am not aware of anything that is broken—maybe it has no effect on aarch64 and is fine. But should this warning not be emitted? Could certain flags be missing from tclConfig.sh for not detecting a 64-bit platform? Might other non-amd64 64-bit Linux platforms be affected?

User Comments:
serhiy.storchaka added on 2026-10-20 12:10:59:

Still present in 8.6, 9.0 and 9.1. On aarch64 the compiler is already 64-bit by default, so nothing is broken: the only effects are the warning and [tcl::pkgconfig get 64bit] being 0. Proposed fix in branch configure-64bit-default, and the same in Tk branch configure-64bit-default: when the compiler does not accept -m64, unix/tcl.m4 checks whether it is 64-bit by default (sizeof(void *) == 8) and accepts that. Checked with a compiler wrapper that rejects -m64, as aarch64 gcc does; x86-64 is unchanged. tclconfig (TEA) has the same check.