Skip to content

fix: disable ngtcp2/nghttp3 in curl build to fix amazonlinux2023 CI#206

Merged
maxday merged 1 commit into
mainfrom
maxday/fix-ci
Jun 17, 2026
Merged

fix: disable ngtcp2/nghttp3 in curl build to fix amazonlinux2023 CI#206
maxday merged 1 commit into
mainfrom
maxday/fix-ci

Conversation

@maxday

@maxday maxday commented Jun 17, 2026

Copy link
Copy Markdown
Member
  • Adds --without-ngtcp2 and --without-nghttp3 to the curl ./configure step in scripts/preinstall.sh
  • Fixes the amazonlinux integration test failure in CI

Amazon Linux 2023's libcurl-devel package now transitively installs ngtcp2-devel 1.21.0. When the bundled curl 7.83.1 runs ./configure, it auto-detects the system ngtcp2 headers and attempts to compile HTTP/3 (QUIC) support. However, curl 7.83.1 was written against an older ngtcp2 API, causing compilation errors like:

  vquic/ngtcp2.c:165:6: error: 'ngtcp2_settings' has no member named 'qlog'
  vquic/ngtcp2.c:195:35: error: unknown type name 'ngtcp2_crypto_level'
  vquic/ngtcp2.c:902:3: error: unknown type name 'ngtcp2_connection_close_error'

Fix: Explicitly disable HTTP/3 dependencies at configure time. The RIC only needs basic HTTP to communicate with the Lambda Runtime API QUIC/HTTP3 support is unnecessary.

Target (OCI, Managed Runtime, both):
both

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Amazon Linux 2023's libcurl-devel now pulls in ngtcp2 1.21.0 as a
dependency, which is API-incompatible with the bundled curl 7.83.1.
Explicitly disable HTTP/3 support since RIC only needs basic HTTP.

@darklight3it darklight3it left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 🚀

@maxday maxday merged commit ced34be into main Jun 17, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants