3.4.x build reports error 65536

[hametan]

Is there an existing issue for this?

• I have searched the existing issues

Kong version ($ kong version)

3.4.x

Current Behavior

3.4.x reports error 65536 on AlmaLinux 10 build

The specific errors are as follows，Hopefully the update will fix this issue.

Warning: Failed searching manifest: Failed loading manifest for https://luarocks.org: Error loading file: [string "/var/cache/luarocks/https___luarocks.org/mani..."]:214163: main function has more than 65536 constants
Warning: Failed searching manifest: Failed loading manifest for https://raw.githubusercontent.com/rocks-moonscript-org/moonrocks-mirror/master/: Error loading file: [string "/var/cache/luarocks/https___raw.githubusercon..."]:214163: main function has more than 65536 constants
Warning: Failed searching manifest: Failed downloading https://luafr.org/luarocks/manifest-5.1 - failed downloading https://luafr.org/luarocks/manifest-5.1

Error: No results matching query were found for Lua 5.1.
To check if it is available for other Lua versions, use --check-lua-versions.
Target //build:kong failed to build
(22:05:31) INFO: Elapsed time: 244.565s, Critical Path: 244.06s
(22:05:31) INFO: 3 processes: 2 internal, 1 local.
(22:05:31) FAILED: Build did NOT complete successfully

Expected Behavior

No response

Steps To Reproduce

No response

Anything else?

No response

[chronolaw]

Could you try the latest kong gateway (3.9.x), I think that we already have many fixes in it, perhaps this issue does not exist anymore.

[hametan]

Could you try the latest kong gateway (3.9.x), I think that we already have many fixes in it, perhaps this issue does not exist anymore.

3.9.x has been fixed, but it seems to still use PCRE 1. For AlmaLinux 10, you still need to package PCRE 1 yourself. Will this be upgraded in the future? Will you consider building official packages based on AlmaLinux 10? When is this expected? I also see that the official enterprise version 3.4.3.20 also has a fix for this issue, but this version is not open source, and the open source version does not have this fix either.