All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Klein <matthias.klein@optimeas.de>
To: "f_l_k@t-online.de" <f_l_k@t-online.de>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: AW: [OE-core] nativesdk-mesa fails to build since upgrade to version 22.0.0
Date: Wed, 16 Mar 2022 08:55:50 +0000	[thread overview]
Message-ID: <AM0PR10MB31074083A00E6603A722973699119@AM0PR10MB3107.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <33fa836d-4905-b46a-4a72-31ccef03693e@t-online.de>

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

Hello Markus,

Thanks for the quick help!

The variant " to remove x11 " seems to build (incrementally). However, the SDK is still building.
After that I will test the variant regarding dri3. After that I will also do a full/clean build.

Afterwards I will report. But it will take a few hours ...

Many greetings,
Matthias

Von: openembedded-core@lists.openembedded.org <openembedded-core@lists.openembedded.org> Im Auftrag von Markus Volk via lists.openembedded.org
Gesendet: Mittwoch, 16. März 2022 09:35
An: openembedded-core@lists.openembedded.org
Betreff: Re: [OE-core] nativesdk-mesa fails to build since upgrade to version 22.0.0


What does happen, if adding dri3 like this?

PACKAGECONFIG:append:class-native = " dri3"

PACKAGECONFIG:append:class-nativesdk = "dri3"




Am 16.03.22 um 09:17 schrieb Markus Volk:
Hi Matthias,

since you have disabled x11 for target ... does it help to also remove it from native and nativesdk ?

PACKAGECONFIG:remove:class-native = " x11"

PACKAGECONFIG:remove:class-nativesdk = " x11"

Regards,

Markus

Am 16.03.22 um 08:40 schrieb Matthias Klein:

Hello,

I am using mesa in conjunction with meta-qt6 without X11/wayland on an iMX6 with etnaviv.

So in a bbappend I have: PACKAGECONFIG:append = " etnaviv".

I use poky with the following DISTRO_FEATURES:
DISTRO_FEATURES:remove = "x11 wayland vulkan 3g nfc nfs zeroconf"
DISTRO_FEATURES:append = " directfb opengl"

Unfortunately, nativesdk-mesa now no longer builds on build via "-c populate_sdk". However, the package for the target still builds.

| ../mesa-22.0.0/meson.build:520: WARNING: cannot auto-detect -mtls-dialect when cross-compiling, using compiler default
|
| ../mesa-22.0.0/meson.build:614:2: ERROR: Problem encountered: kmsro requires dri3 for X11 support

I compared the meson calls on the target and SDK builds:
NOTE: Executing meson -Dshared-glapi=enabled -Dgallium-opencl=disabled -Dglx-read-only-text=true -Dplatforms= -Ddri3=disabled -Degl=enabled -Delf-tls=true -Dgallium-drivers=swrast,etnaviv, virgl -Dllvm=disabled -Dgbm=enabled -Dgles1=enabled -Dgles2=enabled -Dlmsensors=disabled -Dopengl=true -
Dosmesa=false -Dlibunwind=disabled -Dgallium-va=disabled -Dgallium-vdpau=disabled -Dvulkan-drivers= -Dglx=disabled -Dgallium-xa=disabled -Dgallium-xvmc=disabled. ..

NOTE: Executing meson -Dshared-glapi=enabled -Dgallium-opencl=disabled -Dglx-read-only-text=true -Dplatforms=x11 -Ddri3=disabled -Degl=enabled -Delf-tls=true -Dgallium-drivers=swrast, etnaviv -Dllvm=disabled -Dgbm=enabled -Dgles1=disabled -Dgles2=disabled -Dlmsensors=disabled -Dopengl=true -Dosmesa=false -Dlibunwind=disabled -Dgallium-va=disabled -Dgallium-vdpau=disabled -Dvulkan-drivers= -Dgallium-xa=disabled -Dgallium-xvmc=disabled. ..

Does anyone have any idea what I could do to get the SDK built?

Many greetings,
Matthias









[-- Attachment #2: Type: text/html, Size: 7098 bytes --]

  reply	other threads:[~2022-03-16  8:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-16  7:40 nativesdk-mesa fails to build since upgrade to version 22.0.0 Matthias Klein
2022-03-16  8:17 ` Markus Volk
     [not found] ` <16DCCE8EC93DCD97.17060@lists.openembedded.org>
2022-03-16  8:34   ` [OE-core] " Markus Volk
2022-03-16  8:55     ` Matthias Klein [this message]
     [not found]     ` <16DCD0A1D561F84D.17060@lists.openembedded.org>
2022-03-16 16:19       ` AW: " Matthias Klein
2022-03-16 16:29         ` Markus Volk
2022-03-16 16:36         ` Markus Volk

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=AM0PR10MB31074083A00E6603A722973699119@AM0PR10MB3107.EURPRD10.PROD.OUTLOOK.COM \
    --to=matthias.klein@optimeas.de \
    --cc=f_l_k@t-online.de \
    --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 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.