Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] Stripping kernel modules for ARC
Date: Thu, 15 Sep 2016 09:18:58 +0200	[thread overview]
Message-ID: <87a8f9fx5p.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20160915084753.4717445f@free-electrons.com> (Thomas Petazzoni's message of "Thu, 15 Sep 2016 08:47:53 +0200")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

 > Hello,
 > On Wed, 14 Sep 2016 14:29:35 -0700, Daniel Mentz wrote:

 >> I believe there might be a third option where we pass INSTALL_MOD_STRIP=1
 >> to the kernel Makefile when running "make modules_install". It would then
 >> require a change in the Linux kernel Makefile to run a different
 >> strip/objcopy command for ARC. This would contain the details of stripping
 >> .ko files to the Linux kernel build system. Otherwise, we'll have this
 >> cross-dependency between the kernel and buildroot. As soon as the kernel
 >> switches to .eh_frame, buildroot would have to change again.

 > Exactly my thinking. I discovered INSTALL_MOD_STRIP only recently, and
 > I believe we should use it for the kernel instead of having our own
 > logic. This would remove the need for special logic in Buildroot to
 > strip kernel modules, and would leave it to the kernel build system to
 > know how modules should be stripped in an architecture-specific way.

Sounds good. When was this introduced and what about external kernel modules?

-- 
Venlig hilsen,
Peter Korsgaard 

  reply	other threads:[~2016-09-15  7:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-14 11:29 [Buildroot] Stripping kernel modules for ARC Alexey Brodkin
2016-09-14 19:00 ` Arnout Vandecappelle
2016-09-14 19:18 ` Vineet Gupta
2016-09-14 19:57   ` Peter Korsgaard
2016-09-14 20:00     ` Alexey Brodkin
2016-09-14 20:18     ` Vineet Gupta
2016-09-14 20:21       ` Peter Korsgaard
     [not found] ` <CAE2F3rCBwysRFrMf4CD6uLevvfw0TNaZGyptOj6MLDQvGPPwFg@mail.gmail.com>
2016-09-15  6:47   ` Thomas Petazzoni
2016-09-15  7:18     ` Peter Korsgaard [this message]
2016-09-15  7:49       ` Thomas Petazzoni
2016-09-15  8:08         ` Peter Korsgaard
2016-09-15 10:53           ` Alexey Brodkin

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=87a8f9fx5p.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /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