From: Daniel Drake <ddrake@baylibre.com>
To: yocto-patches@lists.yoctoproject.org
Cc: Hongxu Jia <jiahongxujia@163.com>,
Hongxu Jia <hongxujia83@gmail.com>,
Daniel Drake <ddrake@baylibre.com>
Subject: [meta-tensorflow][PATCH] tensorflow.inc: fix fetch of LLVM for XLA
Date: Wed, 28 Oct 2026 12:20:04 +0000 [thread overview]
Message-ID: <20261028122004.93109-1-ddrake@baylibre.com> (raw)
Building tensorflow-lite fails in do_compile when Bazel fetches llvm-raw:
WARNING: Download from https://storage.googleapis.com/mirror.tensorflow.org/github.com/llvm/llvm-project/archive/909041e4802c4b9a2223ca04099f35bf1dbbd460.tar.gz
failed: class java.io.FileNotFoundException GET returned 404 Not Found
...
Error in download_and_extract: java.io.IOException: Error downloading [...]:
Checksum was 00b1077e029fa57e6f2d9ac24936a49acf23ebc051b04f487131116258be6248
but wanted 3f986184ee126677dbd77edb16d6b82c057ec869fefd7a9871979941e52e837a
The archive pinned by XLA is not on mirror.tensorflow.org, and the archive
GitHub now generates for the same LLVM commit has a different checksum, so
the pin can no longer be satisfied from either URL.
Pin the checksum of the archive GitHub currently serves. Future upstream
releases will point to a newer LLVM commit.
Signed-off-by: Daniel Drake <ddrake@baylibre.com>
---
...01-xla-update-sha256-of-LLVM-archive.patch | 28 +++++++++++++++++++
recipes-framework/tensorflow/tensorflow.inc | 1 +
2 files changed, 29 insertions(+)
create mode 100644 recipes-framework/tensorflow/files/0001-xla-update-sha256-of-LLVM-archive.patch
diff --git a/recipes-framework/tensorflow/files/0001-xla-update-sha256-of-LLVM-archive.patch b/recipes-framework/tensorflow/files/0001-xla-update-sha256-of-LLVM-archive.patch
new file mode 100644
index 0000000..3a6cc72
--- /dev/null
+++ b/recipes-framework/tensorflow/files/0001-xla-update-sha256-of-LLVM-archive.patch
@@ -0,0 +1,28 @@
+From: Daniel Drake <ddrake@baylibre.com>
+Subject: [PATCH] xla: update sha256 of LLVM archive
+
+Bazel can no longer fetch llvm-raw. The mirror.tensorflow.org copy of the
+archive returns 404, and the archive GitHub now generates for the same LLVM
+commit has a different checksum than the one pinned here.
+
+Pin the checksum of the archive GitHub currently serves. The LLVM commit is
+unchanged.
+
+Upstream-Status: Inappropriate [workaround for a regenerated GitHub archive; upstream master pins a newer LLVM commit]
+Signed-off-by: Daniel Drake <ddrake@baylibre.com>
+---
+ third_party/xla/third_party/llvm/workspace.bzl | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/third_party/xla/third_party/llvm/workspace.bzl b/third_party/xla/third_party/llvm/workspace.bzl
+--- a/third_party/xla/third_party/llvm/workspace.bzl
++++ b/third_party/xla/third_party/llvm/workspace.bzl
+@@ -5,7 +5,7 @@
+ def repo(name):
+ """Imports LLVM."""
+ LLVM_COMMIT = "909041e4802c4b9a2223ca04099f35bf1dbbd460"
+- LLVM_SHA256 = "3f986184ee126677dbd77edb16d6b82c057ec869fefd7a9871979941e52e837a"
++ LLVM_SHA256 = "00b1077e029fa57e6f2d9ac24936a49acf23ebc051b04f487131116258be6248"
+
+ tf_http_archive(
+ name = name,
diff --git a/recipes-framework/tensorflow/tensorflow.inc b/recipes-framework/tensorflow/tensorflow.inc
index e337519..69bfefc 100644
--- a/recipes-framework/tensorflow/tensorflow.inc
+++ b/recipes-framework/tensorflow/tensorflow.inc
@@ -27,6 +27,7 @@ SRC_URI = "git://github.com/tensorflow/tensorflow.git;branch=r2.21;protocol=http
file://0001-set-x83_64-to-arch-of-whl.patch \
file://0001-fix-compile-failed-with-clang-21.patch \
file://0001-fix-clang-22.patch \
+ file://0001-xla-update-sha256-of-LLVM-archive.patch \
"
DEPENDS += " \
--
2.56.0
next reply other threads:[~2026-10-28 12:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 12:20 Daniel Drake [this message]
2026-10-28 12:30 ` [yocto-patches] [meta-tensorflow][PATCH] tensorflow.inc: fix fetch of LLVM for XLA 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=20261028122004.93109-1-ddrake@baylibre.com \
--to=ddrake@baylibre.com \
--cc=hongxujia83@gmail.com \
--cc=jiahongxujia@163.com \
--cc=yocto-patches@lists.yoctoproject.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.