From: Nicholas Piggin <npiggin@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH] kbuild: provide THIN_ARCHIVES option for all architectures
Date: Tue, 30 May 2017 09:13:43 +1000	[thread overview]
Message-ID: <20170530091343.1f98b24b@roar.ozlabs.ibm.com> (raw)
In-Reply-To: <CA+55aFwofV0DZhh+yGH_=ceBzFcSr_tGexuGV4Wioao096R-uQ@mail.gmail.com>
On Mon, 29 May 2017 10:14:50 -0700
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Mon, May 29, 2017 at 10:03 AM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > So either thin archives work or they don't. Don't make it some painful
> > drawn-out process that actually makes it harder to test rather than
> > easier.  
>
> Side note: what would make them not work? Are there known bugs in 'ar'
> wrt thin archives, versioning issues, or other issues?
We haven't run into any bugs AFAIK. It's been pretty solid.
*thin* archives does require binutils 2.19. That's nearly 10 years
old, but we advertise 2.12 minimum at the moment. We'd have make "T"
an optional argument if we turn it on unconditionally. Regular
archives shouldn't be significantly worse than ld -r though, so yeah
maybe we could do that.
powerpc required a build fix:
43c9127d94d
-override AR    := GNUTARGET=elf$(BITS)-$(GNUTARGET) $(AR)
+KBUILD_ARFLAGS += --target=elf$(BITS)-$(GNUTARGET)
So there could be a couple of small things like this.
Thanks,
Nick
next prev parent reply	other threads:[~2017-05-29 23:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-29  8:11 [PATCH] kbuild: provide THIN_ARCHIVES option for all architectures Nicholas Piggin
2017-05-29 10:33 ` Stephen Rothwell
2017-05-29 14:34   ` Nicholas Piggin
2017-05-29 17:03 ` Linus Torvalds
2017-05-29 17:14   ` Linus Torvalds
2017-05-29 23:13     ` Nicholas Piggin [this message]
2017-05-29 23:13       ` Nicholas Piggin
2017-05-30  3:22       ` Linus Torvalds
2017-05-30  3:55         ` Nicholas Piggin
2017-05-30  3:54       ` Linus Torvalds
2017-05-30  3:54         ` Linus Torvalds
2017-05-29 18:52 ` Sam Ravnborg
2017-05-29 18:52   ` Sam Ravnborg
2017-05-29 23:49   ` Nicholas Piggin
2017-05-31 21:13 ` Arnd Bergmann
2017-06-04 23:17   ` Masahiro Yamada
2017-06-05  7:00     ` Nicholas Piggin
2017-06-05  7:00       ` 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=20170530091343.1f98b24b@roar.ozlabs.ibm.com \
    --to=npiggin@gmail.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --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;
as well as URLs for NNTP newsgroup(s).