Skip to contentSkip to conversation

mesa-native fails on master

DISCUSSION Mark Hatle 5 participants 7 messages Apr 4, 2023

lore
Share & tools
lore

Mark Hatle

author
#0 lore raw

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

#1 lore raw

I just met the same issue. My host is ubuntu18, gcc version is 7.5.0.

Regards,
Qi

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Mark Hatle
Sent: Tuesday, April 4, 2023 10:25 AM
To: Patches and discussions about the oe-core layer <[email protected]>
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

#2 lore raw
Quoted 25 lines · Chen Qi

I just met the same issue. My host is ubuntu18, gcc version is 7.5.0.

Regards,
Qi

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Mark Hatle
Sent: Tuesday, April 4, 2023 10:25 AM
To: Patches and discussions about the oe-core layer <[email protected]>
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

Quoted 6 lines

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.

You need a newer gcc compiler > 7.x
I just abandoned using ubuntu 18.04
see - https://lists.openembedded.org/g/openembedded-core/message/178783?p=%2C%2C%2C20%2C0%2C0%2C0%3A%3Acreated%2C0%2Cnon-trivial+designated+initializers+not+supported%2C20%2C2%2C0%2C97647023

Quoted 29 lines

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/1997914
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

author
#3 lore raw

I'm fine with saying either Ubuntu 18.04 is no longer 'supported', or running some kind of check that says gcc 7.5.0 is too old.. But I'm not sure what minimum (host) compiler version would be needed to avoid this error.

I'm happy to work up a patch to adjust the minimum gcc version, if someone can give me a bit of a clue what the appropriate minimum should be.

The current check (in sanity.bbclass) looks for 7.5 or newer.

--Mark

Quoted 70 lines · Khem Raj
Quoted 25 lines · Chen Qi

I just met the same issue. My host is ubuntu18, gcc version is 7.5.0.

Regards,
Qi

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Mark Hatle
Sent: Tuesday, April 4, 2023 10:25 AM
To: Patches and discussions about the oe-core layer <[email protected]>
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

Quoted 6 lines

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.

You need a newer gcc compiler > 7.x
I just abandoned using ubuntu 18.04
see - https://lists.openembedded.org/g/openembedded-core/message/178783?p=%2C%2C%2C20%2C0%2C0%2C0%3A%3Acreated%2C0%2Cnon-trivial+designated+initializers+not+supported%2C20%2C2%2C0%2C97647023

Quoted 33 lines

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 (#179669): https://lists.openembedded.org/g/openembedded-core/message/179669
Mute This Topic: https://lists.openembedded.org/mt/98052337/3616948
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

#4 lore raw
Quoted 9 lines · Mark Hatle

I'm fine with saying either Ubuntu 18.04 is no longer 'supported', or running some kind of check that says gcc 7.5.0 is too old.. But I'm not sure what minimum (host) compiler version would be needed to avoid this error.

I'm happy to work up a patch to adjust the minimum gcc version, if someone can give me a bit of a clue what the appropriate minimum should be.

The current check (in sanity.bbclass) looks for 7.5 or newer.

https://docs.mesa3d.org/install.html

says it should 8.0.0 or newer. So perhaps that check should be bumped to check for 8.0 in master.

Quoted 74 lines

--Mark

Quoted 70 lines · Khem Raj
Quoted 25 lines · Chen Qi

I just met the same issue. My host is ubuntu18, gcc version is 7.5.0.

Regards,
Qi

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Mark Hatle
Sent: Tuesday, April 4, 2023 10:25 AM
To: Patches and discussions about the oe-core layer <[email protected]>
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

Quoted 6 lines

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.

You need a newer gcc compiler > 7.x
I just abandoned using ubuntu 18.04
see - https://lists.openembedded.org/g/openembedded-core/message/178783?p=%2C%2C%2C20%2C0%2C0%2C0%3A%3Acreated%2C0%2Cnon-trivial+designated+initializers+not+supported%2C20%2C2%2C0%2C97647023

Quoted 33 lines

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 (#179669): https://lists.openembedded.org/g/openembedded-core/message/179669
Mute This Topic: https://lists.openembedded.org/mt/98052337/3616948
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

#5 lore raw
In reply to Chen, Qi
Quoted 1 line · [Re: [OE-core] mesa-native fails on master] On 04/04/2023 (Tue 02:39) Chen Qi…

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

Quoted 59 lines

Regards,
Qi

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Mark Hatle
Sent: Tuesday, April 4, 2023 10:25 AM
To: Patches and discussions about the oe-core layer <[email protected]>
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: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

#6 lore raw
Quoted 8 lines · Paul Gortmaker
Quoted 1 line · [Re: [OE-core] mesa-native fails on master] On 04/04/2023 (Tue 02:39) Chen Qi…

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