Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: michel.thebeau@windriver.com
Cc: Bruce.Ashfield@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] kernel.bbclass: do_strip: allow recipes to strip the kernel
Date: Mon, 08 Apr 2013 21:54:33 +0100	[thread overview]
Message-ID: <1365454473.12407.51.camel@ted> (raw)
In-Reply-To: <1365452153-21650-3-git-send-email-michel.thebeau@windriver.com>

On Mon, 2013-04-08 at 16:15 -0400, michel.thebeau@windriver.com wrote:
> From: Michel Thebeau <michel.thebeau@windriver.com>
> 
> Allow recipes to specify sections to be stripped from the kernel output
> using KERNEL_IMAGE_STRIP_EXTRA_SECTIONS.  For example:
> 
> KERNEL_IMAGE_STRIP_EXTRA_SECTIONS = ".comment .unwanted"
> 
> The file to be stripped is a copy of ${KERNEL_OUTPUT} and will be given
> the same name with an additional ".stripped" suffix.  The suffix can be
> overridden using KERNEL_STRIP_SUFFIX.
> 
> Since the toolchain does not give indication when the specified sections
> are absent, we read the sections first and make this report by issuing a
> warning to the developer.
> 
> The toolchain by default strips the image with the -s option (even
> when -s is not specified):
> -s --strip-all       Remove all symbol and relocation information
> 
> For example, these sections are always removed:
> .debug_aranges
> .debug_info
> .debug_abbrev
> .debug_line
> .debug_frame
> .debug_str
> .debug_loc
> .debug_ranges
> .symtab
> .strtab
> 
> In addition to these, the sections listed in
> KERNEL_IMAGE_STRIP_EXTRA_SECTIONS will also be removed.
> 
> Only stripping of vmlinux (elf) is supported at this time.  A warning
> will be given if the image type is not vmlinux.
> 
> Stripping the image could also be done in the kernel, but that would
> only work for linux-yocto based kernels, so it's not the route we
> decided to go.
> 
> [YOCTO 3515]
> 
> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
> Signed-off-by: Michel Thebeau <michel.thebeau@windriver.com>

Can we please just have one output kernel, not two. Is the unstripped
version useful anywhere?

Cheers,

Richard






  reply	other threads:[~2013-04-08 21:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-08 20:15 [RFC] [PATCH 0/2] Routerstation Pro: kernel.bbclass: do_sizecheck, do_strip michel.thebeau
2013-04-08 20:15 ` [PATCH 1/2] kernel.bbclass: do_sizecheck: update path to build image and do not delete michel.thebeau
2013-04-08 20:15 ` [PATCH 2/2] kernel.bbclass: do_strip: allow recipes to strip the kernel michel.thebeau
2013-04-08 20:54   ` Richard Purdie [this message]
2013-04-08 21:24     ` Michel Thebeau
2013-04-08 21:24     ` michel.thebeau
2013-04-08 21:28       ` Michel Thebeau
2013-04-08 21:48         ` Richard Purdie
2013-04-09 12:44           ` Michel Thebeau
2013-04-08 20:15 ` [poky] [PATCH 1/1] routerstationpro: strip the output kernel of .comment section michel.thebeau

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=1365454473.12407.51.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Bruce.Ashfield@windriver.com \
    --cc=michel.thebeau@windriver.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