Package Details: nginx-quic 1.23.3-1

Git Clone URL: https://aur.archlinux.org/nginx-quic.git (read-only, click to copy)
Package Base: nginx-quic
Description: Lightweight HTTP server and IMAP/POP3 proxy server, HTTP/3 QUIC branch
Upstream URL: https://nginx.org
Keywords: http3 nginx quic webserver
Licenses: custom
Conflicts: nginx
Provides: nginx, nginx-mainline
Submitter: DasSkelett
Maintainer: DasSkelett
Last Packager: DasSkelett
Votes: 9
Popularity: 0.143311
First Submitted: 2020-12-20 02:20 (UTC)
Last Updated: 2022-12-17 20:28 (UTC)

Required by (182)

Sources (4)

Latest Comments

1 2 3 Next › Last »

DasSkelett commented on 2022-10-20 17:10 (UTC)

Updated to nginx-quic 1.23.2, and also applied the changes from @phoepsilonix, thanks for the suggestions!

phoepsilonix commented on 2022-09-14 11:59 (UTC) (edited on 2022-09-14 12:06 (UTC) by phoepsilonix)

To build with clang, add the following option --with-cc-opt="-flto" --with-ld-opt="-flto -fuse-ld=lld"

When clang is used, it is not necessary to modify CFLAGS for gcc bug countermeasures.

# clang
if [[ $CC=="clang" ]];then
    _cc_opt="-flto"
    _ld_opt="-flto -fuse-ld=lld"
fi
    --with-cc-opt="$_cc_opt -I../boringssl/include" \
    --with-ld-opt="$_ld_opt -L../boringssl/build/ssl -L../boringssl/build/crypto" \
-  # Disable some warnings that make Boringssl fail to compile due to a forced -Werror in CMakeLists.txt
-  # -Wno-array-bounds: 2022-05-21 for compatiblity with GCC 12.1 (https://bugs.chromium.org/p/boringssl/issues/detail?id=492&sort=-modified)
-  export CFLAGS="$CFLAGS -fPIC -Wno-stringop-overflow -Wno-array-parameter -Wno-array-bounds"
+  export CFLAGS="$CFLAGS -fPIC"

TheHardew commented on 2022-06-09 10:31 (UTC)

PSA, if your site can't stop loading after enabling http3, you might need to rebuild the modules against nginx-quic-src. At least in my case, nginx did start without errors when loading wrong modules, and I had forgotten to rebuild them so debugging was a little difficult at first.

DasSkelett commented on 2022-05-29 12:06 (UTC)

Ah I see, the problem was that it opened an interactive merging tool for you. This didn't happen for me, as there wasn't any installed, so the hg resolve -t internal:other --all that I added took care of it. I've reverted it now so it doesn't matter anymore anyway, but for the future I now know I'll have to set HGMERGE=false so it doesn't open a merging tool for other people.

Thanks for letting me know and the demonstration, that helped to understand the issue.

kescherAUR commented on 2022-05-29 11:52 (UTC)

There's actually just one merge conflict, I think, and it's the version number: https://asciinema.org/a/bys4JTwDtgBbkaAoA0HcgLsV4?t=33

DasSkelett commented on 2022-05-29 11:27 (UTC)

Hm, I believe I shouldn't have merged with the stable branch anyway, we target mainline only. I don't know if they plan to do a mainline release soon as well, but for now I think I'm going to revert the last commit, which should also avoid the merge conflict problem.

DasSkelett commented on 2022-05-29 10:53 (UTC)

Indeed, but I've added a command to automatically resolve this. Does it not work for you?

kescherAUR commented on 2022-05-29 10:51 (UTC)

There's a merge conflict with the manual 1.22 merge.

DasSkelett commented on 2022-05-18 10:36 (UTC)

Looks like there's a build failure for BoringSSL with GCC 12, I'll look into resolving it, but chances are I'll have to add -Wno-array-bounds to CFLAGS.

In file included from /usr/include/string.h:535,
                 from /aur/nginx-quic/src/boringssl/crypto/x509v3/v3_utl.c:63:
In function ‘memset’,
    inlined from ‘OPENSSL_memset’ at /aur/nginx-quic/src/boringssl/crypto/x509v3/../internal.h:840:10,
    inlined from ‘ipv6_from_asc’ at /aur/nginx-quic/src/boringssl/crypto/x509v3/v3_utl.c:1281:9,
    inlined from ‘x509v3_a2i_ipadd’ at /aur/nginx-quic/src/boringssl/crypto/x509v3/v3_utl.c:1193:14,
    inlined from ‘X509_check_ip_asc’ at /aur/nginx-quic/src/boringssl/crypto/x509v3/v3_utl.c:1113:21:
/usr/include/bits/string_fortified.h:59:10: error: ‘__builtin_memset’ forming offset 16 is out of the bounds [0, 16] of object ‘ipout’ with type ‘unsigned char[16]’ [-Werror=array-bounds]
   59 |   return __builtin___memset_chk (__dest, __ch, __len,
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   60 |                                  __glibc_objsize0 (__dest));
      |                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~
/aur/nginx-quic/src/boringssl/crypto/x509v3/v3_utl.c: In function ‘X509_check_ip_asc’:
/aur/nginx-quic/src/boringssl/crypto/x509v3/v3_utl.c:1108:19: note: ‘ipout’ declared here
 1108 |     unsigned char ipout[16];
      |                   ^~~~~

kescherAUR commented on 2022-02-01 19:45 (UTC)

@DasSkelett It happens for nginx-mainline-mod-brotli-git, for instance