From: Thomas Vandenabeele <thomas@bootzero.one>
To: openembedded-core@lists.openembedded.org
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
Thomas Vandenabeele <thomas@bootzero.one>,
Yoann Congal <yoann.congal@smile.fr>
Subject: [PATCH] [scarthgap] go-vendor: Fix absolute paths issue
Date: Sat, 14 Feb 2026 17:08:06 +0100 [thread overview]
Message-ID: <20260214160806.3043158-1-thomas@bootzero.one> (raw)
From: Richard Purdie <richard.purdie@linuxfoundation.org>
When building with the class, avoid errors like:
"sstate found an absolute path symlink /xxx/vendor pointing at
/xxx/import/vendor. Please replace this with a relative link."
Use relative symlinks instead.
Fixes [OE-Core 15683] in scarthgap
(From OE-Core rev: fc4f589cc7a8e5feba7940ccb244a74bd5f96371)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Thomas Vandenabeele <thomas@bootzero.one>
Cc: Yoann Congal <yoann.congal@smile.fr>
---
meta/classes/go-vendor.bbclass | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/meta/classes/go-vendor.bbclass b/meta/classes/go-vendor.bbclass
index 1bbb99ac79..e58cfaf0e1 100644
--- a/meta/classes/go-vendor.bbclass
+++ b/meta/classes/go-vendor.bbclass
@@ -70,7 +70,7 @@ python do_go_vendor() {
if os.path.exists(vendor_dir):
# Nothing to do except re-establish link to actual vendor folder
if not os.path.exists(linkname):
- os.symlink(vendor_dir, linkname)
+ oe.path.relsymlink(vendor_dir, linkname)
return
bb.utils.mkdirhier(vendor_dir)
@@ -202,10 +202,10 @@ python do_go_vendor() {
symlink_target = os.path.join(source_dir, *['src', go_import, replaced_path])
symlink_name = os.path.join(vendor_dir, vendored_name)
bb.debug(1, "vendored name %s, symlink name %s" % (vendored_name, symlink_name))
- os.symlink(symlink_target, symlink_name)
+ oe.path.relsymlink(symlink_target, symlink_name)
# Create a symlink to the actual directory
- os.symlink(vendor_dir, linkname)
+ oe.path.relsymlink(vendor_dir, linkname)
}
addtask go_vendor before do_patch after do_unpack
reply other threads:[~2026-02-14 16:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260214160806.3043158-1-thomas@bootzero.one \
--to=thomas@bootzero.one \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=yoann.congal@smile.fr \
/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