From: Paul Eggert Date: Mon, 10 Apr 2023 18:55:54 +0000 (-0700) Subject: doc: update re 32-bit builds X-Git-Tag: v9.3~5 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=cc95246ee2ed674cd407f0f80fd77f3364012458;p=thirdparty%2Fcoreutils.git doc: update re 32-bit builds * README-install: Mention how to build on 32-bit-only hosts. This builds on a previous patch by Pádraig Brady. --- diff --git a/README-install b/README-install index 0c5bcf4706..6ab5b4f8c2 100644 --- a/README-install +++ b/README-install @@ -54,13 +54,13 @@ all mention of "[$(EXEEXT)" from src/Makefile. 32 bit time_t build failures ------------------------ -On systems where it's determined that 64 bit time_t is supported -(indicated by touch -t ), but that coreutils -would be built with a narrower time_t, the build will fail. -This can be allowed by passing TIME_T_32_BIT_OK=yes to configure, -or avoided by enabling 64 bit builds. For example GCC on AIX defaults -to 32 bit, and to enable the 64 bit ABI one can use: -./configure CFLAGS=-maix64 LDFLAGs=-maix64 AR='ar -X64' +Although 32-bit builds fail if that forces time_t to be 32 bits, this +can be fixed by using 64-bit builds. For example, on AIX where GCC +defaults to 32 bits, one can use "./configure CC='gcc -maix64' AR='ar +-X64'"; similarly, on Solaris one can configure with CC='gcc -m64'. +If all else fails one can configure with ac_year2038_required=no; +however, this will mishandle timestamps after 2038, and please file +bug reports for any such situations. *************************************************