Skip to content
New issue

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? Sign in to your account

Build yara-x with increased memory, --target-dir for cargo-c, and optimizations #38392

Merged
merged 2 commits into from
Dec 26, 2024

Conversation

egibs
Copy link
Member

@egibs egibs commented Dec 26, 2024

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 redirect cargo-c's build artifacts to a non-/tmp directory to avoid running in to QEMU's noexec tmpfs.

Once this was fixed, the cargo-c install was OOM'ing with the default -m 4000000k configuration so I added a memory requirement of 6Gi which allowed the build to succeed. Finally, I added opt-level=3 to build the yara-x-capi with all available optimizations.

…imizations

Signed-off-by: egibs <20933572+egibs@users.noreply.github.com>
@octo-sts octo-sts bot added the bincapz/pass bincapz/pass Bincapz (aka. malcontent) scan didn't detect any CRITICALs on the scanned packages. label Dec 26, 2024
dannf
dannf previously approved these changes Dec 26, 2024
Copy link
Contributor

@dannf dannf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just a nit inline

yara-x.yaml Outdated Show resolved Hide resolved
Signed-off-by: egibs <20933572+egibs@users.noreply.github.com>
@egibs egibs requested a review from dannf December 26, 2024 17:30
@egibs egibs enabled auto-merge (squash) December 26, 2024 17:58
@egibs egibs merged commit bd3fdfd into wolfi-dev:main Dec 26, 2024
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bincapz/pass bincapz/pass Bincapz (aka. malcontent) scan didn't detect any CRITICALs on the scanned packages.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants