From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] mesa: Up the llvm release to 8.0
Date: Sat, 02 Feb 2019 08:43:07 +0000 [thread overview]
Message-ID: <5823863d849da95bcc1368b60a64ca8f39cff3eb.camel@linuxfoundation.org> (raw)
In-Reply-To: <20190201151929.27893-1-raj.khem@gmail.com>
On Fri, 2019-02-01 at 07:19 -0800, Khem Raj wrote:
> Needs to happen along with llvm upgrade always
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
> meta/recipes-graphics/mesa/mesa.inc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-graphics/mesa/mesa.inc b/meta/recipes-graphics/mesa/mesa.inc
> index e96a12c1b9..66ed649efe 100644
> --- a/meta/recipes-graphics/mesa/mesa.inc
> +++ b/meta/recipes-graphics/mesa/mesa.inc
> @@ -105,7 +105,7 @@ GALLIUMDRIVERS_append = ",virgl"
>
> # keep --with-gallium-drivers separate, because when only one of gallium versions is enabled, other 2 were adding --without-gallium-drivers
> PACKAGECONFIG[gallium] = "--enable-texture-float --with-gallium-drivers=${GALLIUMDRIVERS}, --without-gallium-drivers"
> -MESA_LLVM_RELEASE ?= "6.0"
> +MESA_LLVM_RELEASE ?= "8.0"
> PACKAGECONFIG[gallium-llvm] = "--enable-llvm --enable-llvm-shared-libs, --disable-llvm, llvm${MESA_LLVM_RELEASE} llvm-native \
> ${@'elfutils' if ${GALLIUMDRIVERS_LLVM33_ENABLED} else ''}"
> export WANT_LLVM_RELEASE = "${MESA_LLVM_RELEASE}"
There is something still not right with llvm/mesa:
https://autobuilder.yoctoproject.org/typhoon/#/builders/72/builds/251/steps/7/logs/step8b
Cheers,
Richard
prev parent reply other threads:[~2019-02-02 8:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 15:19 [PATCH] mesa: Up the llvm release to 8.0 Khem Raj
2019-02-02 8:43 ` Richard Purdie [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=5823863d849da95bcc1368b60a64ca8f39cff3eb.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--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