Closed
Description
I did this
I checked recent CI builds. I noticed that both builds on zuul that build quiche (+boringssl) fail consistently. The build ends with:
-- Build files have been written to: /home/zuul/quiche/target/release/build/quiche-986e736b297204f2/out/build
running: "cmake" "--build" "." "--target" "bssl" "--config" "RelWithDebInfo" "--parallel" "8"
--- stderr
Unknown argument --parallel
Unknown argument 8
Usage: cmake --build <dir> [options] [-- [native-options]]
Options:
<dir> = Project binary directory to be built.
--target <tgt> = Build <tgt> instead of default targets.
May only be specified once.
--config <cfg> = For multi-configuration tools, choose <cfg>.
--clean-first = Build target 'clean' first, then build.
(To clean only, use --target 'clean'.)
--use-stderr = Ignored. Behavior is default in CMake >= 3.0.
-- = Pass remaining options to the native tool.
thread 'main' panicked at '
command did not execute successfully, got: exit status: 1
I think this is the boringssl part? It looks like it uses a cmake option that the cmake version used here doesn't support.
I expected the following
All quiche builds to be fine.
curl/libcurl version
current git master
operating system
These builds run on ubuntu-bionic.