Builder curl-unthreaded-solaris11-sparc Build #5468
Results:
Build successful
SourceStamp:
| Project | curl |
| Repository | https://github.com/curl/curl.git |
| Branch | master |
| Revision | 38107d33544f37ccf7bfcd6e82ede079a40c77e8 |
| Got Revision | 38107d33544f37ccf7bfcd6e82ede079a40c77e8 |
| Changes | 3 changes |
BuildSlave:
unstable11sReason:
The SingleBranchScheduler scheduler named 'schedule-curl-unthreaded-solaris11-sparc' triggered this build
Steps and Logfiles:
Build Properties:
| Name | Value | Source |
|---|---|---|
| branch | master | Build |
| builddir | /export/home/buildbot/slave/curl-unthreaded-solaris11-sparc | slave |
| buildername | curl-unthreaded-solaris11-sparc | Builder |
| buildnumber | 5468 | Build |
| codebase | Build | |
| got_revision | 38107d33544f37ccf7bfcd6e82ede079a40c77e8 | Git |
| osplatform | SPARC | SetPropertyFromCommand Step |
| osrelease | 11 | SetPropertyFromCommand Step |
| project | curl | Build |
| repository | https://github.com/curl/curl.git | Build |
| revision | 38107d33544f37ccf7bfcd6e82ede079a40c77e8 | Build |
| scheduler | schedule-curl-unthreaded-solaris11-sparc | Scheduler |
| slavename | unstable11s | BuildSlave |
| workdir | /export/home/buildbot/slave/curl-unthreaded-solaris11-sparc | slave (deprecated) |
Forced Build Properties:
| Name | Label | Value |
|---|
Responsible Users:
- Flavio Amieiroflavio@amieiro.net
- Viktor Szakatscommit@vsz.me
Timing:
| Start | Tue Mar 17 14:45:14 2026 |
| End | Tue Mar 17 15:24:18 2026 |
| Elapsed | 39 mins, 4 secs |
All Changes:
:
Change #261307
Category curl Changed by Flavio Amieiro <flavio@amieiro.net> Changed at Tue 17 Mar 2026 14:34:48 Repository https://github.com/curl/curl.git Project curl Branch master Revision fa5d2cc97e687ee57a069763a3cce5ae85cee9a8 Comments
curl_ctype.h: fix spelling in a couple of locally used macros The `ISLOWHEXALHA` and `ISUPHEXALHA` macros were introduced in commit f65f750 and seem to be only referenced locally by the `ISXDIGIT` macro. Judging by the `ISALPHA` macro defined in the same file, it seems like the intention was to spell them as `IS.*HEXALPHA`. I noticed this while reading through the code and decided to open a PR, even if it is only a tiny change, just because I was already looking at it and it might be useful. If there is any reason not to merge this, please do close the PR. Closes #20810
Changed files
- lib/curl_ctype.h
Change #261308
Category curl Changed by Viktor Szakats <commit@vsz.me> Changed at Tue 17 Mar 2026 14:36:54 Repository https://github.com/curl/curl.git Project curl Branch master Revision 3e74a3e0621fdde141b39ad97db88196e0f8999e Comments
openssl: drop obsolete SSLv2 logic Closes #20945
Changed files
- lib/vtls/openssl.c
Change #261309
Category curl Changed by Viktor Szakats <commit@vsz.me> Changed at Tue 17 Mar 2026 14:37:53 Repository https://github.com/curl/curl.git Project curl Branch master Revision 38107d33544f37ccf7bfcd6e82ede079a40c77e8 Comments
configure: fix `--with-ngtcp2=<path>` option for crypto libs ngtcp2 1.14.0 added module dependencies to `ngtcp2_crypto_*.pc` files. This broke certain build cases in curl, because configure was is querying pkg-config modules by setting `PKG_CONFIG_LIBDIR` to the directory specified via `--with-*=` options, including `--with-ngtcp2=`. Setting `PKG_CONFIG_LIBDIR` tells pkg-config (and pkgconf) to ignore system locations. This caused that `ngtcp2_crypto_gnutls.pc` could no longer find its indirect dependencies, if those were present at system locations (where they typically are). Another fallout was BoringSSL, because it does not provide `openssl.pc` on its own, and successful detection relied on finding a non-BoringSSL copy, typically at a system location (also fixed in ngtcp2 main branch). Fix `ngtcp2_crypto_*` detections to not touch `PKG_CONFIG_LIBDIR` and instead prepend `<path>` set via `--with-ngtcp2=` to `PKG_CONFIG_PATH`. This ensures to pick up any dependent modules from system locations. Note the side-effect is that potentially undesired modules may be detected this way from system locations, i.e. it makes this particular detection less "hermetic" than the rest used in curl configure. (Configurations using a bare `--with-ngtcp2` with no path were not affected, and served as a workaround before this patch. It remains a valid way of configuration after.) Both `pkgconf` and `pkg-config` use this logic to calculate their search directory list: ```pseudo search = {} if PKG_CONFIG_PATH is set search += PKG_CONFIG_PATH endif if PKG_CONFIG_LIBDIR is set (even if empty) search += PKG_CONFIG_LIBDIR else search += built-in-pkg-config-dirs endif ``` Refs: https://github.com/curl/curl/pull/18028/commits (earlier attempt. Failed due to using `PKG_CONFIG_DIR` instead of the correct `PKG_CONFIG_PATH`) https://github.com/curl/curl/pull/18028/commits/c0874ce8242d42a1ae1d570d6b70b8360da56482 https://man.archlinux.org/man/pkgconf.1.en https://manpages.debian.org/unstable/pkgconf/pkgconf.1.en.html https://manpages.debian.org/unstable/pkg-config/pkg-config.1.en.html https://github.com/ngtcp2/ngtcp2/commit/10e27fd63cc7dd87236ab15de4a02eca6801e234 Bug: https://github.com/curl/curl/pull/18022#issuecomment-3120587041 Bug: https://github.com/ngtcp2/ngtcp2/pull/1689#issuecomment-3120593664 Follow-up to 04d90b5deb332cd2359d5ba3f71804c55da14397 #20931 Follow-up to 3c64ffaff4cd8c8275627dd2e17b6879a1d32262 #18415 #18188 Follow-up to 99500660af19f89069e71c2251c13963401b3806 #18028 #18022 Closes #20920Changed files
- .github/workflows/http3-linux.yml
- acinclude.m4
- configure.ac
- docs/HTTP3.md