public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicholas Piggin <npiggin@gmail.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Nicholas Piggin <npiggin@gmail.com>, linux-kbuild@vger.kernel.org
Subject: [PATCH v2 0/3] fix ia64, tile, sh for thin archives
Date: Thu, 22 Jun 2017 22:39:26 +1000	[thread overview]
Message-ID: <20170622123929.15054-1-npiggin@gmail.com> (raw)

This is a re-work of the vdso symbol linking patches to avoid the
problem,

  ld: warning: .note.gnu.build-id  section discarded, --build-id ignored.

I was able to reproduce the problem, and I have compiled
defconfig for 3 architectures here with this new approach
and I saw no problems.

Please replace the existing patches in kbuild/thin-ac with these
3 if you agree with them.

Thanks,
Nick

Nicholas Piggin (3):
  sh: thin archives fix linking
  ia64: thin archives fix linking
  tile: thin archives fix linking

 arch/ia64/kernel/Makefile.gate   | 12 +++++++-----
 arch/sh/kernel/vsyscall/Makefile | 16 +++++++++-------
 arch/tile/kernel/vdso/Makefile   | 14 ++++++++------
 3 files changed, 24 insertions(+), 18 deletions(-)

-- 
2.11.0


             reply	other threads:[~2017-06-22 12:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-22 12:39 Nicholas Piggin [this message]
2017-06-22 12:39 ` [PATCH v2 1/3] sh: thin archives fix linking Nicholas Piggin
2017-06-23  3:25   ` Masahiro Yamada
2017-06-23  3:50     ` Nicholas Piggin
2017-06-23 10:02       ` Masahiro Yamada
2017-06-25  3:24         ` Masahiro Yamada
2017-06-22 12:39 ` [PATCH v2 2/3] ia64: " Nicholas Piggin
2017-06-23  9:56   ` Masahiro Yamada
2017-06-23 13:44     ` Nicholas Piggin
2017-06-25  3:26       ` Masahiro Yamada
2017-06-22 12:39 ` [PATCH v2 3/3] tile: " Nicholas Piggin
2017-06-25  3:28   ` Masahiro Yamada
2017-06-25  5:23     ` Nicholas Piggin
2017-06-23  3:23 ` [PATCH v2 0/3] fix ia64, tile, sh for thin archives Masahiro Yamada
2017-06-23  3:42   ` Nicholas Piggin

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=20170622123929.15054-1-npiggin@gmail.com \
    --to=npiggin@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=yamada.masahiro@socionext.com \
    /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