All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alex.kanavin@gmail.com>
To: alex.kanavin@gmail.com
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
	 openembedded-core@lists.openembedded.org,
	 Alexander Kanavin <alex@linutronix.de>
Subject: Re: [OE-core] [PATCH] mesa: do not rely on native llvm-config in target sysroot
Date: Mon, 14 Nov 2022 17:36:36 +0100	[thread overview]
Message-ID: <CANNYZj9siEQWd8ZT7GZeyApjkNg14CBgSVSjiMFd+M8GHpk-zw@mail.gmail.com> (raw)
In-Reply-To: <CANNYZj-_ZYP6NUBnZu2mOgY2o4x=ZzM4aBnuURVRRehLYiwnjw@mail.gmail.com>

And here's the ticket for meson where this issue originates:
https://github.com/mesonbuild/meson/issues/11043

Apparently llvm-config is not the only, or even the recommended way to
get settings, it's just that meson is using it instead of relying
entirely on cmake configs.

Alex

On Mon, 14 Nov 2022 at 15:25, Alexander Kanavin <alex.kanavin@gmail.com> wrote:
>
> Anyway. I filed an upstream ticket:
> https://github.com/llvm/llvm-project/issues/58984
>
> Alex
>
> On Mon, 14 Nov 2022 at 14:50, Alexander Kanavin via
> lists.openembedded.org <alex.kanavin=gmail.com@lists.openembedded.org>
> wrote:
> >
> > On Mon, 14 Nov 2022 at 14:41, Richard Purdie
> > <richard.purdie@linuxfoundation.org> wrote:
> >
> > > The trouble is how many people are ever going to check whether the
> > > output of llvm-config changes? We really need to work with upstream to
> > > make this util cross safe...
> >
> > Yes, by making it a thin wrapper over pkg-config. I am completely
> > baffled why many projects, llvm included, have some kind of lifetime
> > allergy to pkg-config.
> >
> > Alex
> >
> > -=-=-=-=-=-=-=-=-=-=-=-
> > Links: You receive all messages sent to this group.
> > View/Reply Online (#173243): https://lists.openembedded.org/g/openembedded-core/message/173243
> > Mute This Topic: https://lists.openembedded.org/mt/95018621/1686489
> > Group Owner: openembedded-core+owner@lists.openembedded.org
> > Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [alex.kanavin@gmail.com]
> > -=-=-=-=-=-=-=-=-=-=-=-
> >


      parent reply	other threads:[~2022-11-14 16:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-14 13:35 [PATCH] mesa: do not rely on native llvm-config in target sysroot Alexander Kanavin
2022-11-14 13:40 ` [OE-core] " Richard Purdie
2022-11-14 13:50   ` Alexander Kanavin
     [not found]   ` <172777C031C3B2CB.6692@lists.openembedded.org>
2022-11-14 14:25     ` Alexander Kanavin
2022-11-14 15:23       ` Vincent Davis Jr
2022-11-14 16:36       ` Alexander Kanavin [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=CANNYZj9siEQWd8ZT7GZeyApjkNg14CBgSVSjiMFd+M8GHpk-zw@mail.gmail.com \
    --to=alex.kanavin@gmail.com \
    --cc=alex@linutronix.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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.