Build yara-x with increased memory, --target-dir for cargo-c, and optimizations #38392
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I had some local Melange changes that made #38328 appear valid when in fact the build artifacts for
cargo-c
were still landing in/tmp
.This PR specifies
--target-dir
to redirectcargo-c
's build artifacts to a non-/tmp
directory to avoid running in to QEMU'snoexec
tmpfs.Once this was fixed, the
cargo-c
install was OOM'ing with the default-m 4000000k
configuration so I added a memory requirement of6Gi
which allowed the build to succeed. Finally, I addedopt-level=3
to build theyara-x-capi
with all available optimizations.