From: Mark Hatle <mark.hatle@kernel.crashing.org>
To: openembedded-core@lists.openembedded.org
Cc: mark.hatle@amd.com
Subject: [PATCH v2 1/4] package.py: Fix static debuginfo split
Date: Thu, 18 Jul 2024 18:27:59 -0500 [thread overview]
Message-ID: <1721345282-10901-2-git-send-email-mark.hatle@kernel.crashing.org> (raw)
In-Reply-To: <1721345282-10901-1-git-send-email-mark.hatle@kernel.crashing.org>
From: Mark Hatle <mark.hatle@amd.com>
Fix:
NameError: name 'shutil' is not defined
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org>
---
meta/lib/oe/package.py | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/lib/oe/package.py b/meta/lib/oe/package.py
index e6b46a0..8a64e13 100644
--- a/meta/lib/oe/package.py
+++ b/meta/lib/oe/package.py
@@ -838,6 +838,8 @@ def splitdebuginfo(file, dvar, dv, d):
return (file, sources)
def splitstaticdebuginfo(file, dvar, dv, d):
+ import shutil
+
# Unlike the function above, there is no way to split a static library
# two components. So to get similar results we will copy the unmodified
# static library (containing the debug symbols) into a new directory.
--
1.8.3.1
next prev parent reply other threads:[~2024-07-18 23:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 23:27 [PATCH v2 0/4] Fix static-library related issues Mark Hatle
2024-07-18 23:27 ` Mark Hatle [this message]
2024-07-19 14:32 ` [OE-core] [PATCH v2 1/4] package.py: Fix static debuginfo split Richard Purdie
2024-07-18 23:28 ` [PATCH v2 2/4] package.py: Fix inode link target Mark Hatle
2024-07-18 23:28 ` [PATCH v2 3/4] package.py: Fix static library processing Mark Hatle
2024-07-18 23:28 ` [PATCH v2 4/4] selftest-hardlink: Add additional test cases Mark Hatle
2024-07-19 6:49 ` [OE-core] " Richard Purdie
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=1721345282-10901-2-git-send-email-mark.hatle@kernel.crashing.org \
--to=mark.hatle@kernel.crashing.org \
--cc=mark.hatle@amd.com \
--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