From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Alexis Lothoré" <alexis.lothore@bootlin.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/openscap: set dependency on C++ support
Date: Mon, 16 Feb 2026 10:56:40 +0100 [thread overview]
Message-ID: <aZLpW6VY-EmXGyn-@windsurf> (raw)
In-Reply-To: <20260216-openscap_cpp-v1-1-3372149da5b0@bootlin.com>
Hello Alexis,
Thanks for the fix!
On Mon, Feb 16, 2026 at 10:40:42AM +0100, Alexis Lothoré wrote:
> When the toolchain involved in openscap build does not support C++, the
> configure step fails with the following error:
>
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - failed
> -- Check for working CXX compiler: /bin/false
> -- Check for working CXX compiler: /bin/false - broken
> CMake Error at /usr/share/cmake/Modules/CMakeTestCXXCompiler.cmake:73 (message):
> The C++ compiler
From a quick look, it doesn't seem like openscap contains C++ code. So
instead the right fix is most likely to change CMakeLists.txt to check
for the C compiler only.
To do that, in CMakeLists.txt, change:
project(blabla)
to
project(blabla C)
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-02-16 9:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 9:40 [Buildroot] [PATCH] package/openscap: set dependency on C++ support Alexis Lothoré via buildroot
2026-02-16 9:56 ` Thomas Petazzoni via buildroot [this message]
2026-02-16 12:59 ` Alexis Lothoré via buildroot
2026-02-16 14:23 ` Thomas Petazzoni 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=aZLpW6VY-EmXGyn-@windsurf \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox