From: Alexander Kanavin <alex.kanavin@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Alexander Kanavin <alex@linutronix.de>
Subject: [PATCH 11/18] llvm: update 14.0.0 -> 14.0.1
Date: Wed, 27 Apr 2022 10:40:02 +0200 [thread overview]
Message-ID: <20220427084009.3406717-11-alex@linutronix.de> (raw)
In-Reply-To: <20220427084009.3406717-1-alex@linutronix.de>
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
---
meta/conf/distro/include/tcmode-default.inc | 2 +-
meta/recipes-devtools/llvm/llvm_git.bb | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/meta/conf/distro/include/tcmode-default.inc b/meta/conf/distro/include/tcmode-default.inc
index 2200af5b60..3f28514554 100644
--- a/meta/conf/distro/include/tcmode-default.inc
+++ b/meta/conf/distro/include/tcmode-default.inc
@@ -26,7 +26,7 @@ QEMUVERSION ?= "6.2%"
GOVERSION ?= "1.18%"
# This can not use wildcards like 8.0.% since it is also used in mesa to denote
# llvm version being used, so always bump it with llvm recipe version bump
-LLVMVERSION ?= "14.0.0"
+LLVMVERSION ?= "14.0.1"
RUSTVERSION ?= "1.59%"
PREFERRED_VERSION_gcc ?= "${GCCVERSION}"
diff --git a/meta/recipes-devtools/llvm/llvm_git.bb b/meta/recipes-devtools/llvm/llvm_git.bb
index e10348a7f2..53ae1abd57 100644
--- a/meta/recipes-devtools/llvm/llvm_git.bb
+++ b/meta/recipes-devtools/llvm/llvm_git.bb
@@ -19,14 +19,14 @@ inherit cmake pkgconfig
PROVIDES += "llvm${PV}"
-PV = "14.0.0"
+PV = "14.0.1"
MAJOR_VERSION = "${@oe.utils.trim_version("${PV}", 1)}"
LLVM_RELEASE = "${PV}"
BRANCH = "release/${MAJOR_VERSION}.x"
-SRCREV = "329fda39c507e8740978d10458451dcdb21563be"
+SRCREV = "c62053979489ccb002efe411c3af059addcb5d7d"
SRC_URI = "git://github.com/llvm/llvm-project.git;branch=${BRANCH};protocol=https \
file://0006-llvm-TargetLibraryInfo-Undefine-libc-functions-if-th.patch;striplevel=2 \
file://0007-llvm-allow-env-override-of-exe-path.patch;striplevel=2 \
--
2.30.2
next prev parent reply other threads:[~2022-04-27 8:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 8:39 [PATCH 01/18] libxml2: update patch status Alexander Kanavin
2022-04-27 8:39 ` [PATCH 02/18] python3-psutil: submit patch upstream Alexander Kanavin
2022-04-27 8:39 ` [PATCH 03/18] gnu-config: update to latest revision Alexander Kanavin
2022-04-27 8:39 ` [PATCH 04/18] go-helloworld: " Alexander Kanavin
2022-04-27 8:39 ` [PATCH 05/18] piglit: " Alexander Kanavin
2022-04-27 8:39 ` [PATCH 06/18] vulkan-samples: " Alexander Kanavin
2022-04-27 8:39 ` [PATCH 07/18] python3-typing-extensions: upgrade 3.10.0.0 -> 4.2.0 Alexander Kanavin
2022-04-27 8:39 ` [PATCH 08/18] python3-pyparsing: upgrade 3.0.7 -> 3.0.8 Alexander Kanavin
2022-04-27 8:40 ` [PATCH 09/18] glib: upgrade 2.72.0 -> 2.72.1 Alexander Kanavin
2022-04-27 8:40 ` [PATCH 10/18] go: update 1.18 -> 1.18.1 Alexander Kanavin
2022-04-28 16:22 ` [OE-core] " Steve Sakoman
2022-04-28 17:03 ` Khem Raj
2022-04-28 18:00 ` Steve Sakoman
2022-04-28 20:36 ` Khem Raj
2022-04-27 8:40 ` Alexander Kanavin [this message]
2022-04-27 8:40 ` [PATCH 12/18] meson: update 0.61.3 -> 0.62.1 Alexander Kanavin
2022-04-27 8:40 ` [PATCH 13/18] valgrind: update 3.18.1 -> 3.19.0 Alexander Kanavin
2022-04-27 13:08 ` [OE-core] " Richard Purdie
2022-04-27 14:34 ` Alexander Kanavin
2022-04-27 14:37 ` Richard Purdie
2022-04-27 8:40 ` [PATCH 14/18] icu: update 70.1 -> 71.1 Alexander Kanavin
2022-04-27 8:40 ` [PATCH 15/18] libcap-ng: update 0.8.2 -> 0.8.3 Alexander Kanavin
2022-04-27 8:40 ` [PATCH 16/18] libgpg-error: 1.44 -> 1.45 Alexander Kanavin
2022-04-27 8:40 ` [PATCH 17/18] cmake: update 3.23.0 -> 3.23.1 Alexander Kanavin
2022-04-27 8:40 ` [PATCH 18/18] stress-ng: upgrade 0.13.12 -> 0.14.00 Alexander Kanavin
2022-05-05 13:57 ` [OE-core] " Luca Ceresoli
2022-05-05 15:18 ` Alexander Kanavin
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=20220427084009.3406717-11-alex@linutronix.de \
--to=alex.kanavin@gmail.com \
--cc=alex@linutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox