All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin Jansa" <Martin.Jansa@gmail.com>
To: Andrei Gherzan <andrei@gherzan.com>
Cc: Khem Raj <raj.khem@gmail.com>,
	openembedded <openembedded-devel@lists.openembedded.org>
Subject: Re: [oe] [meta-oe][dunfell][PATCH] nss: Disable Werror across all recipe types
Date: Tue, 23 Feb 2021 18:30:02 +0100	[thread overview]
Message-ID: <20210223173002.aydz4xm65ylvgy4k@jama> (raw)
In-Reply-To: <7536ac24-0016-45e2-9cfe-209b50633c8a@www.fastmail.com>

[-- Attachment #1: Type: text/plain, Size: 946 bytes --]

On Tue, Feb 23, 2021 at 05:19:16PM +0000, Andrei Gherzan wrote:
> On Tue, 23 Feb 2021, at 17:15, Khem Raj wrote:
> > On Tue, Feb 23, 2021 at 9:12 AM Martin Jansa <martin.jansa@gmail.com> wrote:
> > >
> > > On Tue, Feb 23, 2021 at 04:27:05PM +0000, Andrei Gherzan wrote:
> > > > From: Khem Raj <raj.khem@gmail.com>
> > > >
> > > > We are seeing warnigs with gcc-10 even on target builds e.g.
> > >
> > > Do you use gcc-10 in dunfell builds?
> > >
> > > dunfell has 9.3.0 gcc, so either you're using gcc-10 through some
> > > backports or the warning is reproducible also with gcc-9, but I'm not
> > > seeing nss failures in my dunfell builds.
> > 
> > I think its the native one he is running into issues. Perhaps he has
> > newer build host OS which has gcc 10
> 
> That is indeed the case. I'm running 10.2.0 on my host as of now.

_on your host_, but why is it needed for target builds which should use
gcc-cross-* 9.3.0?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 201 bytes --]

  reply	other threads:[~2021-02-23 17:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-23 16:27 [meta-oe][dunfell][PATCH] nss: Disable Werror across all recipe types Andrei Gherzan
2021-02-23 17:12 ` [oe] " Martin Jansa
2021-02-23 17:15   ` Khem Raj
2021-02-23 17:19     ` Andrei Gherzan
2021-02-23 17:30       ` Martin Jansa [this message]
2021-02-23 17:47         ` Andrei Gherzan
2021-02-23 21:30           ` Andrei Gherzan
2021-02-23 21:37             ` Martin Jansa
2021-02-23 21:39               ` Andrei Gherzan
2021-02-23 22:28                 ` Andrei Gherzan

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=20210223173002.aydz4xm65ylvgy4k@jama \
    --to=martin.jansa@gmail.com \
    --cc=andrei@gherzan.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=raj.khem@gmail.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.