public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: gavrosc@yahoo.com, openembedded-core@lists.openembedded.org
Cc: Yoann Congal <yoann.congal@smile.fr>
Subject: Re: [OE-core] [PATCH v3] sanity: test for c toolchain
Date: Mon, 20 Jan 2025 13:42:23 +0000	[thread overview]
Message-ID: <0cf72b0f1033722e4c197ae1bcf7891e1d34f65d.camel@linuxfoundation.org> (raw)
In-Reply-To: <20250118120105.11681-1-gavrosc@yahoo.com>

On Sat, 2025-01-18 at 13:01 +0100, Christos Gavros via lists.openembedded.org wrote:
> Users reported issues caused by missing the right libstdc++-version-dev.
> A new function 'check_c_toolchain' added in sanity.bbclass to test linking libstdc++
> Fixes [YOCTO #15712]
> 
> Signed-off-by: Christos Gavros <gavrosc@yahoo.com>
> Reviewed-by: Yoann Congal <yoann.congal@smile.fr>
> ---
> v2->v3
> * whitespaces are removed
> * the format for reference to the bug is fixed
> * 'Reviewed-by' tag is added
> ---
>  meta/classes-global/sanity.bbclass | 40 ++++++++++++++++++++++++++++++
>  1 file changed, 40 insertions(+)

This is looking really good thanks!

The one thing left which probably needs tweaking is testing this on
every build. I think that is a bit too much overhead and we should do
this in check_sanity_version_change().

The reason being that once builds are working on a given system we
probably don't need to check again. If people do run into issues, they
will probably test a clean builddir and at that point the error would
also show up.

If you could send a v4 with that small tweak, I think it looks good to
merge, thanks.

Cheers,

Richard



  reply	other threads:[~2025-01-20 13:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250118120105.11681-1-gavrosc.ref@yahoo.com>
2025-01-18 12:01 ` [PATCH v3] sanity: test for c toolchain Christos Gavros
2025-01-20 13:42   ` Richard Purdie [this message]
2025-01-20 20:35     ` Christos Gavros

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=0cf72b0f1033722e4c197ae1bcf7891e1d34f65d.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=gavrosc@yahoo.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=yoann.congal@smile.fr \
    /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