public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: 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, 4 Apr 2023 10:10:19 -0400	[thread overview]
Message-ID: <ZCwvy2ZBt/0R0/S/@windriver.com> (raw)
In-Reply-To: <CO6PR11MB5602C3D93B44F41049BBDCECED939@CO6PR11MB5602.namprd11.prod.outlook.com>

[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.

Paul.
--

> 
> Regards,
> Qi
> 
> -----Original Message-----
> From: openembedded-core@lists.openembedded.org <openembedded-core@lists.openembedded.org> On Behalf Of Mark Hatle
> Sent: Tuesday, April 4, 2023 10:25 AM
> To: Patches and discussions about the oe-core layer <openembedded-core@lists.openembedded.org>
> Subject: [OE-core] mesa-native fails on master
> 
> It's been a few weeks since I last built master, but starting with today's pull I'm getting errors building mesa-native -- which pretty much kills the whole build.
> 
> I'm on an Ubuntu 18.04 host, and have the 'buildtools-tarball' from the last
> 4.1.3 loaded so I can get to the minimum version of python to run a build.
> 
> (I tried with buildtools-tarball-extended and that DOES appear to work.  If this is expected, you can ignore the rest of this.  But I expected the system to complain before trying to build everything if the compiler wasn't new enough.)
> 
> 
> The error is:
> 
> brw_simd_selection.cpp:205:7: sorry, unimplemented: non-trivial designated initializers not supported
> 
> 
> The host gcc is 7.5.0
> 
> What is strange is I had 2 successful builds, and then it started failing.  All 
> fresh builds.  I've no idea why one was successful and the others failed.  I'm 
> wondering if maybe there is some sort of race in mesa, but lowered my parallel 
> build (-j) to 1 and I'm still getting it.
> 
> 
> Reproducer:
> 
> git clone https://git.yoctoproject.org/poky
> 
> cd poky
> 
> wget 
> http://downloads.yoctoproject.org/releases/yocto/yocto-4.1.3/buildtools/x86_64-buildtools-nativesdk-standalone-4.1.3.sh
> 
> bash x86_64-buildtools-nativesdk-standalone-4.1.3.sh -d buildtools -y
> 
> . ./buildtools/environment-...
> 
> . ./oe-init-build-env
> 
> bitbake mesa-native
> 
> 

> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#179667): https://lists.openembedded.org/g/openembedded-core/message/179667
> Mute This Topic: https://lists.openembedded.org/mt/98052337/6329300
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [paul.gortmaker@windriver.com]
> -=-=-=-=-=-=-=-=-=-=-=-
> 



  parent reply	other threads:[~2023-04-04 14:10 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 [this message]
2023-04-04 14:15     ` Richard Purdie

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=ZCwvy2ZBt/0R0/S/@windriver.com \
    --to=paul.gortmaker@windriver.com \
    --cc=Qi.Chen@windriver.com \
    --cc=mark.hatle@kernel.crashing.org \
    --cc=openembedded-core@lists.openembedded.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