From: "Adinath Mhatre" <adimhatre303@gmail.com>
To: poky@lists.yoctoproject.org
Subject: Dunfell Kernel modules debug info
Date: Thu, 1 Sep 2022 20:26:38 +0530 [thread overview]
Message-ID: <CAGB4t6XXRUOqH3879RMA1J6Zt4Ne9cELfXRnmfW4Wk4Aw37NjA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 812 bytes --]
Hi,
Recently I have upgraded from Yocto Warrior to Dunfell, in which I observe
a major file size increase in /lib/modules.
After debugging found out, in dunfell by default Kernel modules are getting
built with debug_info, which results in file size increase.
For Dunfell
$file demo.ko
demo.ko: ELF 32-bit LSB relocatable, ARM, EABI5 version 1 (SYSV),
BuildID[sha1]=cb8a24d71c5cf4b87ccac5416e2e716e119a285a, with debug_info,
not stripped
For Warrior
$file demo.ko
demo.ko: ELF 32-bit LSB relocatable, ARM, EABI5 version 1 (SYSV),
BuildID[sha1]=6e4de309f358f27105285428a43dd74ee1ae665d, not stripped
According to default Yocto behavior, debug info should not be included
unless we specify "INHIBIT_PACKAGE_DEBUG_SPLIT".
Regards,
Adinath Mhatre
[-- Attachment #2: Type: text/html, Size: 2630 bytes --]
reply other threads:[~2022-09-01 14:56 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=CAGB4t6XXRUOqH3879RMA1J6Zt4Ne9cELfXRnmfW4Wk4Aw37NjA@mail.gmail.com \
--to=adimhatre303@gmail.com \
--cc=poky@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).