From: Jarod Wilson <jarod@redhat.com>
To: Nicolas Pitre <nicolas.pitre@linaro.org>,
Paul Bolle <pebolle@tiscali.nl>
Cc: Tony Luck <tony.luck@intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Prarit Bhargava <prarit@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: Odd build breakage in 4.9-rc7
Date: Fri, 2 Dec 2016 17:41:33 -0500 [thread overview]
Message-ID: <6276dd2d-b2da-67a5-96b2-0a1b5d1be8a2@redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1612021456160.13571@knanqh.ubzr>
On 2016-12-02 3:11 PM, Nicolas Pitre wrote:
> On Thu, 1 Dec 2016, Paul Bolle wrote:
>
>> On Thu, 2016-12-01 at 12:42 -0500, Nicolas Pitre wrote:
>>> OK I understand what the problem is. However most of those hunks below
>>> are definitely wrong. ;-)
>>
>> Probably. By now I've narrowed it down to just these two hunks:
>
> And they're both wrong. ;-) There is no relation between MODVERSIONS and
> TRIM_UNUSED_KSYMS.
>
>>> I'm trying to determine the best way to fix it. Stay tuned.
>>
>> Will do. I'm curious to see what a proper fix might look like.
>
> Here it is:
>
> ----- >8
> Subject: kbuild: fix building bzImage with CONFIG_TRIM_UNUSED_KSYMS enabled
>
> When building a specific target such as bzImage, modules aren't normally
> built. However if CONFIG_TRIM_UNUSED_KSYMS is enabled, no built modules
> means none of the exported symbols are used and therefore they will all
> be trimmed away from the final kernel. A subsequent "make modules" will
> fail because modpost cannot find the needed symbols for those modules in
> the kernel binary.
>
> Let's make sure modules are also built whenever CONFIG_TRIM_UNUSED_KSYMS
> is enabled and that the kernel binary is properly rebuilt accordingly.
For my previously failing case, things behave again with this patch.
Thanks much!
Tested-by: Jarod Wilson <jarod@redhat.com>
--
Jarod Wilson
jarod@redhat.com
prev parent reply other threads:[~2016-12-02 22:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 17:24 Jarod Wilson
2016-11-30 18:18 ` Linus Torvalds
2016-11-30 18:28 ` Prarit Bhargava
2016-11-30 18:36 ` Linus Torvalds
2016-11-30 18:50 ` Prarit Bhargava
2016-11-30 19:00 ` Jarod Wilson
2016-11-30 19:35 ` Linus Torvalds
2016-11-30 22:41 ` Nicolas Pitre
2016-12-01 12:47 ` Prarit Bhargava
2016-12-01 14:03 ` Prarit Bhargava
2016-12-01 15:22 ` Jarod Wilson
2016-11-30 22:54 ` Nicolas Pitre
2016-11-30 20:52 ` Paul Bolle
2016-11-30 21:07 ` Jarod Wilson
2016-11-30 21:35 ` Jarod Wilson
2016-11-30 21:42 ` Paul Bolle
2016-11-30 21:57 ` Paul Bolle
2016-11-30 23:40 ` Jarod Wilson
2016-12-01 9:01 ` Paul Bolle
2016-12-01 13:46 ` Paul Bolle
2016-12-01 17:42 ` Nicolas Pitre
2016-12-01 20:15 ` Paul Bolle
2016-12-02 20:11 ` Nicolas Pitre
2016-12-02 22:41 ` Jarod Wilson [this message]
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=6276dd2d-b2da-67a5-96b2-0a1b5d1be8a2@redhat.com \
--to=jarod@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.pitre@linaro.org \
--cc=pebolle@tiscali.nl \
--cc=prarit@redhat.com \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®