From: Sam Ravnborg <sam@ravnborg.org>
To: Alan Modra <amodra@gmail.com>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Andi Kleen <andi@firstfloor.org>,
mmarek@suse.cz, Cary Coutant <ccoutant@google.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [RFC] kbuild: drop use of "ld -r" for intermediate links of vmlinux
Date: Tue, 18 Feb 2014 22:48:01 +0100 [thread overview]
Message-ID: <20140218214801.GA25163@ravnborg.org> (raw)
In-Reply-To: <20140218145856.GZ3386@bubble.grove.modra.org>
On Wed, Feb 19, 2014 at 01:28:56AM +1030, Alan Modra wrote:
> On Sun, Feb 16, 2014 at 09:37:24PM +0100, Sam Ravnborg wrote:
> > The trick used is that for each directory a linker script is
> > generated that name all the file to be linked - and for
> > sub-directories this is just the linker script for that directory.
> >
> > The file continue to be named "built-in.o" but it is really a linker script.
>
> You'll need binutils newer than 2012-06-25
> https://sourceware.org/ml/binutils/2012-06/msg00201.html
>
> > I recall the idea is from someone else - but have long lost memory of
> > from where I saw it.
>
> I think it might have been my idea originally, implemented by Stephen
> Rothwell.
Sounds right - added in cc:
>
> Another possibility is to use thin archives to package up the objects.
> Thin archives are like normal archives except they just contain paths
> to the objects, not the object contents. Paths are flattened when
> adding one thin archive to another. I think Stephen may have tried
> that idea too.
I just coded this in a similar simple fashion.
It broke building vdso - needs to look into that and will get back when I may
understand why my link suddenly broke.
Thanks for the feedback!
Sam
next prev parent reply other threads:[~2014-02-18 21:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-16 20:37 [RFC] kbuild: drop use of "ld -r" for intermediate links of vmlinux Sam Ravnborg
2014-02-18 14:58 ` Alan Modra
2014-02-18 21:48 ` Sam Ravnborg [this message]
2014-02-19 1:01 ` Alan Modra
2014-02-20 17:02 ` Sam Ravnborg
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=20140218214801.GA25163@ravnborg.org \
--to=sam@ravnborg.org \
--cc=amodra@gmail.com \
--cc=andi@firstfloor.org \
--cc=ccoutant@google.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=sfr@canb.auug.org.au \
/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