Builder curl-unthreaded-solaris11-i386 Build #4764

Results:

Build successful

SourceStamp:

BuildSlave:

Reason:

The SingleBranchScheduler scheduler named 'schedule-curl-unthreaded-solaris11-i386' triggered this build

Steps and Logfiles:

1. git update ( 11 secs )
   1. stdio
2. Runtest './tests/testcurl.pl --nogitpull ...' ( 52 mins, 42 secs )
   1. stdio
   2. resultlog
3. Mail result 'cat resultlog ...' ( 0 secs )
   1. stdio

Build Properties:

Forced Build Properties:

Responsible Users:

1. Viktor Szakats

   commitohnoyoudont@vsz.me

Timing:

All Changes:

:

1. Change #261242

   Category	curl
   Changed by	Viktor Szakats <commitohnoyoudont@vsz.me>
   Changed at	Tue 17 Mar 2026 00:42:41
   Repository	https://github.com/curl/curl.git
   Project	curl
   Branch	master
   Revision	e05cfd6454a9483d72ee8170501686ebd5663390

   Comments

   build: drop `openssl` module dependency for BoringSSL from `libcurl.pc`
   BoringSSL does not provide pc files, as of v0.20260211.0 (and its latest
   main branch.) It also did not provide them in the past.
   
   Its sibling fork, AWS-LC does provide them since v1.18.0 (2023-12-04):
   https://github.com/aws/aws-lc/commit/7e6aef83ecf7bec3a0c6d38e38c64ac079647c78
   https://github.com/aws/aws-lc/pull/1310
   
   Introduce internal variable `OPENSSL_IS_AWSLC` to make this possible.
   
   Bug: https://github.com/curl/curl/pull/20926#issuecomment-4063674714
   Ref: https://github.com/ngtcp2/ngtcp2/pull/1689#issuecomment-4063725461
   
   Closes #20938

   Changed files

   • CMakeLists.txt
   • configure.ac
   • m4/curl-openssl.m4

2. Change #261248

   Category	curl
   Changed by	Viktor Szakats <commitohnoyoudont@vsz.me>
   Changed at	Tue 17 Mar 2026 02:47:05
   Repository	https://github.com/curl/curl.git
   Project	curl
   Branch	master
   Revision	1e3c2bec7eb735736755e15a48701f5b2d5b5979

   Comments

   GHA/http3-linux: add CI reproducer for `--with-ngtcp2=<path>` regression
   Configure LibreSSL autotools job with `--with-ngtcp=<path>` instead of
   adding ngtcp2 to `PKG_CONFIG_PATH`. To test this way of configuration in
   CI and test for the regression reported in #20889.
   
   Turns out this way of configuration isn't affected by the detection
   issue in this particular case.
   
   It also works for other backends except for these two, subject to
   separate fixes:
   - BoringSSL fix: https://github.com/ngtcp2/ngtcp2/pull/2070
   - GnuTLS fix and BoringSSL workaround: #20920
   
   Follow-up to 666db801963afca671ee5fa83bd2e9ed79fb8886 #20891
   Follow-up to 8db0e286b363ad788d6dc0779d605b83c7ed4caf #18189
   Follow-up to 99500660af19f89069e71c2251c13963401b3806 #18028 #18022
   
   Closes #20926

   Changed files

   • .github/workflows/http3-linux.yml