Compilation of brotli for nginx fails since version 1.27.0 on Rocky Linux 8
Nikolaos Milas
nmilas at noa.gr
Tue Sep 3 19:48:30 UTC 2024
On 3/9/2024 9:57 μ.μ., Kevin Weis via nginx wrote:
> ...
> I was able to reproduce your exact error and find a solution that
> should meet your needs, using the current Rocky Linux 8 container
> image from https://hub.docker.com/_/rockylinux with the image id of
> c79048e50f5f.
>
> My solution in short: Install the package `brotli-devel`.
> ...
Hi Kevin,
You are the man! Yes, it works this way!
I am wondering (sorry if the question is naive): Since I am compiling
from source, shouldn't the source code include all necessary modules?
Why an OS package (brotli-devel) should be required?
If the source code does not include some required modules, could /
should we clone some additional code from brotli git to generate the
modules instead of using brotli-devel package?
I am asking because I fear (possibly falsely) that at some point
brotli-devel and brotli source might belong to different software
versions and thus the compilation might then be impossible or generate
inoperative modules.
Thanks a lot for your kind help.
Cheers,
Nick
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4466 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20240903/041c4a20/attachment.bin>
More information about the nginx
mailing list