Bug 2348 - Cleanup package.bbclass - runstrip and split_and_strip_files checks for kernel modules
Summary: Cleanup package.bbclass - runstrip and split_and_strip_files checks for kerne...
Status: RESOLVED FIXED
Alias: None
Product: Meta-yocto
Classification: Build System, Metadata & Runtime
Component: meta-yocto (show other bugs)
Version: 1.2
Hardware: x86 Multiple
: Medium enhancement
Target Milestone: 6.1
Assignee: Sam Kent
QA Contact:
URL:
Whiteboard: NEWCOMER
Depends on:
Blocks:
 
Reported: 2012-04-19 14:25 UTC by Mark Hatle
Modified: 2026-08-20 15:17 UTC (History)
11 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Hatle 2012-04-19 14:25:59 UTC
runstrip and split_and_strip_files checks do not match how they find kernel objects.

Also the strip function for kernel objects preserves dates, while the regular strip function does not.

Finally debug info is not preserved for kernel modules.  This may be something we want to start doing in the future.
Comment 1 Randy MacLeod 2019-06-06 15:26:24 UTC
The code has changed a bit but the idea is likely still valid.
Comment 2 Mateusz Hercuń 2025-09-29 11:44:46 UTC
Hello. I want to fix this issue but I'm not sure what it means 'runstrip and split_and_strip_files checks do not match how they find kernel objects.'
Comment 3 Randy MacLeod 2025-10-01 21:51:45 UTC
Mateusz,

It's great that you want to work on this.

I only have a minute but this might get you started:

poky.git on master
❯ rg "def runstrip"
meta/lib/oe/package.py
22:def runstrip(file, elftype, strip, extra_strip_sections=''):

❯ rg split_and_strip_files  meta/classes-global/package.bbclass
22:# d) split_and_strip_files - split the files into runtime and debug and strip them.
532:    oe.package.process_split_and_strip_files(d)


Take a look at those files and search docs.yoctoproject.org and
then come back with more questions.
Comment 4 Sam Kent 2026-04-21 11:06:18 UTC
Hi

I'm new to contributing and had a look at this to start with something straight forward whilst getting used to using a mailing list

Submitted a patch (hopefully correctly) to the mailing list

https://lists.openembedded.org/g/openembedded-core/topic/patch_1_2_package_py_fix/118935412
Comment 5 Randy MacLeod 2026-04-21 16:42:59 UTC
Thanks Sam.
I've given this enhancement to you.
We're just wrapping up the 6.0 release so your patch may not be merged 
until after that's done, say next week.

Have you read:
https://docs.yoctoproject.org/contributor-guide/index.html
and did you think there was anything missing from that guide?

I see your patches but I'm not the right person to review them.


Welcome to the team!
../Randy
Comment 6 Randy MacLeod 2026-04-27 16:57:49 UTC
Sam, 

Patch reviewed on weekly meeting and is okay but needs a self-test.
Paul will reply on the list and point you in the right direction.
Comment 7 Sam Kent 2026-04-28 12:43:11 UTC
Thanks, I've submitted a V2 with a self test
I used Claude to help get to grips with oe-selftest and have updated the commit message according to the contributor guidelines
Comment 8 Mathieu Dubois-Briand 2026-08-20 12:56:58 UTC
Patch got merged: https://git.openembedded.org/openembedded-core/commit/?id=2f32e6a01cdd18c3a7ade348c7a50b0cd459590f

Mark, can we close the bug entry?
Comment 9 Randy MacLeod 2026-08-20 15:17:46 UTC
RP says fixed.

Thanks Sam!