mirror of
https://github.com/open-goal/jak-project
synced 2026-09-11 20:41:41 -04:00
Alexander J. Semenuk
5d5e35fb9b
## Problem Windows builds break with a current local toolchain (Scoop LLVM 22.1.8, CMake 4.4.0, VS 2026), in two independent ways: 1. The build stops at curl's deliberate guard: `#error "no non-blocking method was found/used/set"` in `third-party/curl/lib/nonblock.c`. 2. From the second configure onward, `cmake --build` re-runs CMake in an endless loop (observed 42 consecutive reconfigure cycles in a single build). Likely the same mechanism behind the "endlessly building" VS 2026 note in `docs/setup/dev/vs.md`. ## Root cause 1. `third-party/curl/CMake/CurlTests.c` passes `int *` to `ioctlsocket()`, whose third parameter is `u_long *`. Clang 22 promotes `-Wincompatible-pointer-types` to a hard error in C, so the `HAVE_IOCTLSOCKET_FIONBIO` try_compile silently fails and `curl_config.h` never defines it. Upstream CI does not see this because the windows-2022 runner image ships an older LLVM. GCC 14 promotes the same warning to a hard error, which is very likely the `CurlTests.c.obj` failure reported from MSYS2 in open-goal/jak-project#3551. Upstream curl hit the identical problem with GCC 14 and fixed the probe in curl 8.8.0 (curl/curl#13578). 2. The root CMakeLists copies the build tree's `compile_commands.json` into `<src>/build/` for clangd using `configure_file()`, which registers its input as a configure dependency. CMake rewrites `compile_commands.json` late in every generation, after `CTestTestfile.cmake` and `cmake_install.cmake` (outputs of the same Ninja regen rule), so once the dependency is registered the rule is deterministically dirty and every `ninja` invocation re-runs CMake. A pristine first configure is safe (the file does not exist yet, so the `if(EXISTS ...)` guard skips the copy), which is why the loop looks machine- or IDE-specific. ## Fix 1. Per review, re-vendor `third-party/curl` at the `curl-8_21_0` tag (previously `curl-8_3_0`), which carries the upstream probe fix plus two years of upstream development; `vendor.yaml` updated to match. Adjustments the version jump forced: - curl 8.15 removed the native macOS Secure Transport backend (`CURL_USE_SECTRANSP`), so macOS now builds curl against OpenSSL like Linux. The two macOS workflows install Homebrew `openssl@3` and export `OPENSSL_ROOT_DIR` (keg-only), and the macOS setup docs gained the same two lines. - `CURL_BROTLI` / `CURL_ZSTD` switched to AUTO-detection in curl 8.10; pinned OFF to keep the previous no-compression behavior and avoid silently linking whatever the CI images happen to have. - curl's new top-level `BUILD_EXAMPLES` cache option (default ON) leaked into discord-rpc's identically named option and broke configure at a nonexistent `examples/send-presence` directory; pinned OFF ahead of the third-party subdirectories. The diff is dominated by the mechanical tag-tree swap under `third-party/curl` (linguist-vendored, collapsed in review). The hand-written changes are `CMakeLists.txt`, the two macOS workflows, `docs/setup/system/macos.md`, and `vendor.yaml`. 2. Swap `configure_file()` for `file(COPY ...)`: the same clangd copy with no configure dependency registered. (`file(COPY_FILE ... ONLY_IF_DIFFERENT)` would be cleaner still but requires CMake 3.21, above the declared `cmake_minimum_required(VERSION 3.10)`.) ## Test plan - [x] Fresh `cmake --preset Release-windows-clang` (LLVM 22, no cache seeding) completes and logs `Enabled SSL backends: Schannel`; the FIONBIO probe passes without the previous `#error` - [x] Full Windows Release build from scratch in the branch worktree (all 1422 targets) - [x] goalc-test suite: 1509 passed, 0 failed - [x] Second consecutive configure with `compile_commands.json` present: the regen rule in `build.ninja` has no `compile_commands.json` input; `<src>/build/compile_commands.json` is still refreshed for clangd - [x] Repeated `ninja` invocations after a full build no longer re-run CMake - [x] macOS Intel and ARM CI green (first exercise of the OpenSSL backend switch) --- I work off a self-hosted forge, so this GitHub account is quiet; the configure logs and ninja dirty-node traces from the investigation are available if anyone wants the raw data. (AI-assisted)
67 lines
2.0 KiB
Markdown
Vendored
Generated
67 lines
2.0 KiB
Markdown
Vendored
Generated
---
|
|
c: Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
|
|
SPDX-License-Identifier: curl
|
|
Long: range
|
|
Short: r
|
|
Help: Retrieve only the bytes within RANGE
|
|
Arg: <range>
|
|
Protocols: HTTP FTP SFTP FILE
|
|
Category: http ftp sftp file
|
|
Added: 4.0
|
|
Multi: single
|
|
See-also:
|
|
- continue-at
|
|
- append
|
|
Example:
|
|
- --range 22-44 $URL
|
|
---
|
|
|
|
# `--range`
|
|
|
|
Retrieve a byte range (i.e. a partial document) from an HTTP/1.1, FTP or SFTP
|
|
server or a local FILE. Ranges can be specified in a number of ways.
|
|
|
|
## 0-499
|
|
specifies the first 500 bytes
|
|
|
|
## 500-999
|
|
specifies the second 500 bytes
|
|
|
|
## -500
|
|
specifies the last 500 bytes
|
|
|
|
## 9500-
|
|
specifies the bytes from offset 9500 and forward
|
|
|
|
## 0-0,-1
|
|
specifies the first and last byte only(*)(HTTP)
|
|
|
|
## 100-199,500-599
|
|
specifies two separate 100-byte ranges(*) (HTTP)
|
|
|
|
##
|
|
|
|
(*) = NOTE that if specifying multiple ranges and the server supports it then
|
|
it replies with a multiple part response that curl returns as-is. It
|
|
contains meta information in addition to the requested bytes. Parsing or
|
|
otherwise transforming this response is the responsibility of the caller.
|
|
|
|
Only digit characters (0-9) are valid in the 'start' and 'stop' fields of the
|
|
'start-stop' range syntax. If a non-digit character is given in the range, the
|
|
server's response is unspecified, depending on the server's configuration.
|
|
|
|
Many HTTP/1.1 servers do not have this feature enabled, so that when you
|
|
attempt to get a range, curl instead gets the whole document.
|
|
|
|
FTP and SFTP range downloads only support the simple 'start-stop' syntax
|
|
(optionally with one of the numbers omitted). FTP use depends on the extended
|
|
FTP command SIZE.
|
|
|
|
When using this option for HTTP uploads using POST or PUT, functionality is
|
|
not guaranteed. The HTTP protocol has no standard interoperable resume upload
|
|
and curl uses a set of headers for this purpose that once proved working for
|
|
some servers and have been left for those who find that useful.
|
|
|
|
This command line option is mutually exclusive with --continue-at: you can only
|
|
use one of them for a single transfer.
|