From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: a.thoma@rational-online.com,
"poky@lists.yoctoproject.org" <poky@lists.yoctoproject.org>
Subject: Re: [poky] [PATCH] gcc sanitizers also build statically for dunfell
Date: Mon, 05 Sep 2022 10:50:24 +0100 [thread overview]
Message-ID: <73881ce034592324fe3dc387fa4bbaad9849dccf.camel@linuxfoundation.org> (raw)
In-Reply-To: <DB4PR10MB626484D5E6016A888599727AA57F9@DB4PR10MB6264.EURPRD10.PROD.OUTLOOK.COM>
On Mon, 2022-09-05 at 09:21 +0000, Thoma, Alexander via lists.yoctoproject.org wrote:
> From ba6cdecb93c09e1f218542a3cfbeb63d9141e069 Mon Sep 17 00:00:00 2001
> From: Alexander Thoma a.thoma@rational-online.com
> Date: Fri, 5 Aug 2022 08:41:09 +0200
> Subject: [PATCH] gcc-sanitizers: modify to also build static libs
>
> gcc-sanitizers static-dev can be build for static and dynamic linking. Before static-dev package was always empty since static build was not enabled.
> Package-dependencies needs to be rearranged since both dev and static-dev need the obj-files.
>
> Signed-off-by: Alexander Thoma a.thoma@rational-online.com
> Signed-off-by: Florian Wuehr f.wuehr@rational-online.com
> ---
> meta/recipes-devtools/gcc/gcc-sanitizers.inc | 43 +++++++++++++++-----
> 1 file changed, 32 insertions(+), 11 deletions(-)
>
This needs to go to the OE-Core list. Also, which release is this
against? It looks like it is against something older like dunfell and
wouldn't work with master.
Cheers,
Richard
parent reply other threads:[~2022-09-05 9:50 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <DB4PR10MB626484D5E6016A888599727AA57F9@DB4PR10MB6264.EURPRD10.PROD.OUTLOOK.COM>]
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=73881ce034592324fe3dc387fa4bbaad9849dccf.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=a.thoma@rational-online.com \
--cc=poky@lists.yoctoproject.org \
/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;
as well as URLs for NNTP newsgroup(s).