On 4/17/24 12:46, 'Mark Rotteveel' via firebird-devel wrote:
> On 17/04/2024 03:07, Adriano dos Santos Fernandes wrote:
>> I'm updating Linux docker build to use GCC 13.2.
>>
>> This looks simple for x64, arm32 and arm64.
>>
>> But it already showed some problems to do for x86, as i386/ubuntu docker
>> image stuck in 18.04.
>>
>> It may be possible to use different strategy (as the arm ones with qemu
>> together with the x64 image), but I want to be sure: we will going to
>> continue supporting Linux (FWIW here) x86?
>
> As a data point (from
>
https://api.github.com/repos/FirebirdSQL/firebird/releases), the
> Firebird-5.0.0.1306-0-linux-x86.tar.gz artifact was download 444 times
> from GitHub, which is about the same as the 440 times of
> Firebird-5.0.0.1306-0-linux-arm64.tar.gz, but a lot less than the 2720
> of Firebird-5.0.0.1306-0-linux-x64.tar.gz.
>
Suppose >99% of that 444 installations are done on x64 linux, probably
some people later replace it with correct one later (for SS 4Gb limit is
very restrictive for big DBs).
Next, x86_64/x64/amd64 is currently often referenced as just x86.
Starting with linux kernel - resulting binary bzImage is built in
/usr/src/linux/arch/x86/boot, /usr/src/linux/arch/x86_64/boot contains
only symlink to it. That's more or like we do not call 32-bit binaries
x686, just x86, though it certainly can not run on plain 8086. I.e. many
users are sure they download correctly chosen binary but get not what
they really need.