URL: <https://savannah.gnu.org/support/?111111>
Summary: AC_SYS_LARGEFILE system wide control and autoconf
releases
Group: Autoconf
Submitter: rpetrov
Submitted: Sun 25 Aug 2024 08:46:40 AM UTC
Priority: 5 - Unprioritized
Severity: 1 - Wish
Status: None
Privacy: Public
Assigned to: None
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Operating System: None
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: Sun 25 Aug 2024 08:46:40 AM UTC By: Румен Петров <rpetrov>
Main question is how to effectively control "64-bits" on 32-bits OS in long
term period.
== Introduction ==
Usually Linux package name encode Linux release and architecture.
Process is slightly different for Android application. It coverer a wide range
of OS-releases starting from so called MinSDK(API level).
Use of 64-bit variables is not useful as some functionality is available from
different API level. Issue are well document in bionic documentation.
To ensure working binaries for all OS releases starting from API level MinSDK
my configuration scripts defines a number of "cache variable" as system wide
configuration for Android builds.
One is do not activate "large files" so that binaries could be used on minimum
supported API level.
== Issue ==
Autoconf 2.72 changes _cv_ used to control large files. As result "non
updated" configure script detects "64 bits" support. This is not useful for 32
bit Android. Actually is wrong.
== Questions ==
(1) How to be sure that script working with Autoconf <= 2.71 and adapted to
Autoconf 2.72 will work with future Autoconf releases?
(2) Would autoconf "Cache-Variable-Index" list those related (used) in
AC_SYS_LARGEFILE macro?
Regards,
Roumen Petrov
Not member of autconf mailing lists.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/support/?111111>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
