public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Kai <kai.kang@windriver.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Khem Raj <raj.khem@gmail.com>, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v2] mesa: Add native patch via a variable
Date: Wed, 19 Oct 2022 13:55:09 +0800	[thread overview]
Message-ID: <b43c49da-a285-1c6c-3ebf-d6c38c4326f1@windriver.com> (raw)
In-Reply-To: <CANNYZj8sYJ9-RfzTAwpiiPSmmSRQvrjhTyFYPn-hub0eSUC2PA@mail.gmail.com>

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

On 10/19/22 13:50, Alexander Kanavin wrote:
> Come to think of it, the right thing to do is to actually not do 
> anything at all, just adjust the patch explaining that it is needed on 
> 18.04 hosts. Is there a problem when it is applied for the target?

It fails to compile mesa-native on 18.04 if DEBUG_BUILD enabled. But it 
fails to compile mesa with that patch.

Kai

>
> Alex
>
> On Wed 19. Oct 2022 at 7.42, Alexander Kanavin via 
> lists.openembedded.org 
> <https://urldefense.com/v3/__http://lists.openembedded.org__;!!AjveYdw8EvQ!eZulY7DjDKYv2r3yzQn8Vn8UN9xivFvCN3petJXB1tdJL1wXemB_puMLwiTRps7xFdrrlqhC7Jmgij04C42w4jI$> 
> <alex.kanavin=gmail.com@lists.openembedded.org> wrote:
>
>     Can you show examples where this is needed? Custom variable does
>     not seem a good idea. I also worry that it’ll break automated
>     updates (it’s bad enough with mesa-gl, this might make it worse)
>
>     Alex
>
>     On Wed 19. Oct 2022 at 1.08, Khem Raj <raj.khem@gmail.com> wrote:
>
>         This helps override the SRC_URI in entirety if needed by
>         and overriding recipe
>
>         Signed-off-by: Khem Raj <raj.khem@gmail.com>
>         Cc: Kai Kang <kai.kang@windriver.com>
>         ---
>         v2: Weakly define NATIVE_PATCHES
>
>          meta/recipes-graphics/mesa/mesa.inc | 5 +++--
>          1 file changed, 3 insertions(+), 2 deletions(-)
>
>         diff --git a/meta/recipes-graphics/mesa/mesa.inc
>         b/meta/recipes-graphics/mesa/mesa.inc
>         index c94e439363..04d78a6aa5 100644
>         --- a/meta/recipes-graphics/mesa/mesa.inc
>         +++ b/meta/recipes-graphics/mesa/mesa.inc
>         @@ -19,10 +19,11 @@ SRC_URI =
>         "https://mesa.freedesktop.org/archive/mesa-${PV}.tar.xz
>         <https://urldefense.com/v3/__https://mesa.freedesktop.org/archive/mesa-$*7BPV*7D.tar.xz__;JSU!!AjveYdw8EvQ!eZulY7DjDKYv2r3yzQn8Vn8UN9xivFvCN3petJXB1tdJL1wXemB_puMLwiTRps7xFdrrlqhC7Jmgij04FmSFkx8$>
>         \
>         file://0001-meson-misdetects-64bit-atomics-on-mips-clang.patch \
>         file://0001-futex.h-Define-__NR_futex-if-it-does-not-exist.patch \
>         file://0001-util-format-Check-for-NEON-before-using-it.patch \
>         +           ${NATIVE_PATCHES} \
>                     "
>         -
>         +NATIVE_PATCHES ?= ""
>          # required by mesa-native on Ubuntu 18.04 with gcc 7.5 when
>         DEBUG_BUILD enabled
>         -SRC_URI:append:class-native = "
>         file://0001-nir-nir_opt_move-fix-ALWAYS_INLINE-compiler-error.patch"
>         +NATIVE_PATCHES:class-native =
>         "file://0001-nir-nir_opt_move-fix-ALWAYS_INLINE-compiler-error.patch"
>
>          SRC_URI[sha256sum] =
>         "b1f9c8fd08f2cae3adf83355bef4d2398e8025f44947332880f2d0066bdafa8c"
>
>         -- 
>         2.38.0
>
>
>
>
>
>     -=-=-=-=-=-=-=-=-=-=-=-
>     Links: You receive all messages sent to this group.
>     View/Reply Online (#171954):
>     https://lists.openembedded.org/g/openembedded-core/message/171954
>     <https://urldefense.com/v3/__https://lists.openembedded.org/g/openembedded-core/message/171954__;!!AjveYdw8EvQ!eZulY7DjDKYv2r3yzQn8Vn8UN9xivFvCN3petJXB1tdJL1wXemB_puMLwiTRps7xFdrrlqhC7Jmgij04ZTM5SzE$>
>     Mute This Topic:
>     https://lists.openembedded.org/mt/94420106/1686489
>     <https://urldefense.com/v3/__https://lists.openembedded.org/mt/94420106/1686489__;!!AjveYdw8EvQ!eZulY7DjDKYv2r3yzQn8Vn8UN9xivFvCN3petJXB1tdJL1wXemB_puMLwiTRps7xFdrrlqhC7Jmgij04N8vN8aQ$>
>     Group Owner: openembedded-core+owner@lists.openembedded.org
>     <mailto:openembedded-core%2Bowner@lists.openembedded.org>
>     Unsubscribe:
>     https://lists.openembedded.org/g/openembedded-core/unsub
>     <https://urldefense.com/v3/__https://lists.openembedded.org/g/openembedded-core/unsub__;!!AjveYdw8EvQ!eZulY7DjDKYv2r3yzQn8Vn8UN9xivFvCN3petJXB1tdJL1wXemB_puMLwiTRps7xFdrrlqhC7Jmgij047kVLbgo$>
>     [alex.kanavin@gmail.com]
>     -=-=-=-=-=-=-=-=-=-=-=-
>

-- 
Kai Kang
Wind River Linux

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

  reply	other threads:[~2022-10-19  5:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18 23:08 [PATCH v2] mesa: Add native patch via a variable Khem Raj
2022-10-19  5:42 ` [OE-core] " Alexander Kanavin
2022-10-19  6:34   ` Khem Raj
2022-10-19  6:54     ` Alexander Kanavin
2022-10-19 15:04       ` Khem Raj
     [not found]     ` <171F65F5948858B5.6129@lists.openembedded.org>
2022-10-19 10:35       ` Alexander Kanavin
2022-10-26 14:34         ` Mark Hatle
2022-10-26 16:03           ` Alexander Kanavin
2022-10-26 17:20             ` Mark Hatle
2022-10-26 17:48               ` Joshua Watt
2022-10-26 18:01                 ` Alexander Kanavin
2022-10-27  0:46                   ` Mark Hatle
2022-10-28 10:59                     ` Alexander Kanavin
2022-10-28 18:01                       ` Mark Hatle
2022-10-26 20:58                 ` Mark Hatle
2022-10-19 15:29     ` Ross Burton
2022-10-19 16:04       ` Alexander Kanavin
2022-10-26 14:13         ` Richard Purdie
2022-10-19 16:05       ` Martin Jansa
2022-10-21 21:59       ` Khem Raj
     [not found] ` <171F61FEE1540458.9064@lists.openembedded.org>
2022-10-19  5:50   ` Alexander Kanavin
2022-10-19  5:55     ` Kai [this message]
2022-10-19  5:58     ` Martin Jansa

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=b43c49da-a285-1c6c-3ebf-d6c38c4326f1@windriver.com \
    --to=kai.kang@windriver.com \
    --cc=alex.kanavin@gmail.com \
    --cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox