public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Paul Gortmaker <paul.gortmaker@windriver.com>, Qi.Chen@windriver.com
Cc: Mark Hatle <mark.hatle@kernel.crashing.org>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] mesa-native fails on master
Date: Tue, 04 Apr 2023 15:15:55 +0100	[thread overview]
Message-ID: <d1c3bc3d76cec7f805f8a5d26aefb6b5701b0dce.camel@linuxfoundation.org> (raw)
In-Reply-To: <ZCwvy2ZBt/0R0/S/@windriver.com>

On Tue, 2023-04-04 at 10:10 -0400, Paul Gortmaker wrote:
> [Re: [OE-core] mesa-native fails on master] On 04/04/2023 (Tue 02:39) Chen Qi via lists.openembedded.org wrote:
> 
> > I just met the same issue. My host is ubuntu18, gcc version is 7.5.0.
> 
> Note that ubuntu-18.04 is End-of-Life in another three weeks (unless you
> buy additional support) - in case people weren't keeping track.
> 
> The ubuntu-20.04 uses gcc-9.4.0 by default.

OpenSUSE of various versions and 18.04 use gcc 7.5. We already require
buildtools tarball for both so making gcc 8 the minimum seems fine. As
you say, 18.04 will start to disappear soon anyway.

Cheers,

Richard


      reply	other threads:[~2023-04-04 14:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-04  2:24 mesa-native fails on master Mark Hatle
2023-04-04  2:39 ` [OE-core] " Chen, Qi
2023-04-04  2:48   ` Khem Raj
2023-04-04  2:56     ` Mark Hatle
2023-04-04  3:04       ` Khem Raj
2023-04-04 14:10   ` Paul Gortmaker
2023-04-04 14:15     ` Richard Purdie [this message]

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=d1c3bc3d76cec7f805f8a5d26aefb6b5701b0dce.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Qi.Chen@windriver.com \
    --cc=mark.hatle@kernel.crashing.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.gortmaker@windriver.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