From: "Alexis Lothoré via buildroot" <buildroot@buildroot.org>
To: buildroot@buildroot.org
Cc: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Alexis Lothoré" <alexis.lothore@bootlin.com>
Subject: [Buildroot] [PATCH v2 0/2] package/openscap: fix and test build failure related to crypto
Date: Mon, 07 Sep 2026 15:47:35 +0200 [thread overview]
Message-ID: <20260907-fix_openscap-v2-0-28f8f6ee3248@bootlin.com> (raw)
Hello,
this is v2 of a small series aiming to fix an openscap build failure
occuring when no crypto backend is selected (this can currently happen
on master if openscap AND static libs are selected). The initial
revision is a few months old; the upstream openscap project has fixed
the root issue since then (being able to build openscap without any
crypto backend), so the new patch is quite different from the original.
The series now also exposes some small tests to exercize the different
ways of building openscap.
Signed-off-by: Alexis Lothoré <alexis.lothore@bootlin.com>
---
Changes in v2:
- go further and allow openscap to build without any crypto backend
- add tests for openscap with different crypto backends
- Link to v1: https://patch.msgid.link/20260616-fix_openscap-v1-1-e02d43887309@bootlin.com
To: buildroot@buildroot.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Alexis Lothoré <alexis.lothore@bootlin.com>
---
Alexis Lothoré (2):
package: openscap: fix build failure when crypto backend is not gcrypt
support/testing: add tests for openscap
.../0001-Fix-build-without-crypto-support.patch | 57 ++++++++++++++++++++
...gcrypt-cmake-variables-if-gcrypt-is-not-f.patch | 50 +++++++++++++++++
package/openscap/Config.in | 5 --
package/openscap/openscap.mk | 9 ++--
support/testing/tests/package/test_openscap.py | 63 ++++++++++++++++++++++
.../rootfs-overlay/root/benchmark.xml | 5 ++
6 files changed, 178 insertions(+), 11 deletions(-)
---
base-commit: 87e95b9877ffd29ce9a02399b8a008266a1f5971
change-id: 20260616-fix_openscap-410e397f7257
Best regards,
--
Alexis Lothoré <alexis.lothore@bootlin.com>
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2026-09-07 13:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 13:47 Alexis Lothoré via buildroot [this message]
2026-09-07 13:47 ` [Buildroot] [PATCH v2 1/2] package: openscap: fix build failure when crypto backend is not gcrypt Alexis Lothoré via buildroot
2026-09-07 13:47 ` [Buildroot] [PATCH v2 2/2] support/testing: add tests for openscap Alexis Lothoré via buildroot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260907-fix_openscap-v2-0-28f8f6ee3248@bootlin.com \
--to=buildroot@buildroot.org \
--cc=alexis.lothore@bootlin.com \
--cc=thomas.petazzoni@bootlin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.