public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: Jarod Wilson <jarod@redhat.com>, 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: Thu, 01 Dec 2016 21:15:31 +0100	[thread overview]
Message-ID: <1480623331.22912.3.camel@tiscali.nl> (raw)
In-Reply-To: <alpine.LFD.2.20.1612011238480.1715@knanqh.ubzr>

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:

diff --git a/scripts/Makefile b/scripts/Makefile
index 1d80897a9644..f23e5c4f2496 100644
--- a/scripts/Makefile
+++ b/scripts/Makefile
@@ -40,7 +40,9 @@ build_docproc: $(obj)/docproc
 build_check-lc_ctype: $(obj)/check-lc_ctype
 	@:
 
-subdir-$(CONFIG_MODVERSIONS) += genksyms
+ifeq ($(or $(CONFIG_MODVERSIONS),$(CONFIG_TRIM_UNUSED_KSYMS)),y)
+subdir-y                     += genksyms
+endif
 subdir-y                     += mod
 subdir-$(CONFIG_SECURITY_SELINUX) += selinux
 subdir-$(CONFIG_DTC)         += dtc
diff --git a/scripts/adjust_autoksyms.sh b/scripts/adjust_autoksyms.sh
index 8dc1918b6783..7525da1cc2f7 100755
--- a/scripts/adjust_autoksyms.sh
+++ b/scripts/adjust_autoksyms.sh
@@ -68,7 +68,7 @@ while read sym; do
 done >> "$new_ksyms_file"
 
 # Special case for modversions (see modpost.c)
-if [ -n "$CONFIG_MODVERSIONS" ]; then
+if [ -n "$CONFIG_MODVERSIONS" -o -n "$CONFIG_TRIM_UNUSED_KSYMS" ]; then
 	echo "#define __KSYM_module_layout 1" >> "$new_ksyms_file"
 fi
 

> 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.

Thanks,


Paul Bolle

  reply	other threads:[~2016-12-01 20:15 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-30 17:24 Odd build breakage in 4.9-rc7 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 [this message]
2016-12-02 20:11                     ` Nicolas Pitre
2016-12-02 22:41                       ` Jarod Wilson

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=1480623331.22912.3.camel@tiscali.nl \
    --to=pebolle@tiscali.nl \
    --cc=jarod@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas.pitre@linaro.org \
    --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