From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Gyorgy Sarvari" <skandigraun@gmail.com>,
<openembedded-devel@lists.openembedded.org>
Cc: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Martin Jansa" <martin.jansa@gmail.com>
Subject: Re: [oe] [meta-oe PATCH v4] cryptopp: add a recipe for version 8.9.0
Date: Wed, 04 Jun 2025 15:16:57 +0200 [thread overview]
Message-ID: <DADS05TNTW47.2RJD9AAHCUP7I@bootlin.com> (raw)
In-Reply-To: <2cf31147-fa1a-4277-892d-a6b89648ed5e@gmail.com>
On Wed Jun 4, 2025 at 12:33 PM CEST, Gyorgy Sarvari wrote:
> On 6/4/25 10:54, Antonin Godard via lists.openembedded.org wrote:
>> Cryptopp is a library of cryptographic schemes written in C++.
>>
>> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
>> ---
>> Note: I had no issue building with MACHINE to "qemux86-64" and TCLIBC =
>> "musl", as reported here:
>> https://lore.kernel.org/r/CAMKF1sreBnjjX0GW-G9+15Y+EgFQUmKUPX_cqYE7J3WaZ9=94g@mail.gmail.com
>> Any extra steps to reproduce the issue would be appreciated.
> Looking at the linked logs, Khem was using clang - and indeed,
> 'TOOLCHAIN = "clang"' reproduces the error on my end.
Thanks for the hint, I'll try that.
> If there will be a v5, could you also add "tag" to the SRC_URI?
And thanks for the reminder!
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-06-04 13:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-04 8:54 [meta-oe PATCH v4] cryptopp: add a recipe for version 8.9.0 Antonin Godard
2025-06-04 10:33 ` [oe] " Gyorgy Sarvari
2025-06-04 13:16 ` Antonin Godard [this message]
2025-06-04 23:23 ` Khem Raj
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=DADS05TNTW47.2RJD9AAHCUP7I@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=skandigraun@gmail.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.