Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
to your account
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"
Unknown argument --parallel
Unknown argument 8
Usage: cmake --build <dir> [options] [-- [native-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.
All quiche builds to be fine.
current git master
These builds run on ubuntu-bionic.
The text was updated successfully, but these errors were encountered:
@ghedo can you make sense of this? Is this the boringssl build from within quiche and if so, do you know if we can make it not use the --parallel option?
Sorry, something went wrong.
Ubuntu bionic ships with cmake 3.10
The cmake --parallel command line option was introduced in cmake 3.12.
... yet the boringssl CMakeLists.txt file says:
zuul: build quiche with BoringSSL built separately
... in an attempt to avoid BoringSSL using cmake --parallel because
that's an option that doesn't exist in the cmake shipped in Ubuntu
Bionic, which is a system commonly used in our CI systems.
Successfully merging a pull request may close this issue.