All of lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 20 Feb 2014 18:02:09 +0100	[thread overview]
Message-ID: <20140220170209.GA5103@ravnborg.org> (raw)
In-Reply-To: <20140219010100.GA3386@bubble.grove.modra.org>

On Wed, Feb 19, 2014 at 11:31:00AM +1030, Alan Modra wrote:
> On Tue, Feb 18, 2014 at 10:48:01PM +0100, Sam Ravnborg wrote:
> > > 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.
> 
> Missing --whole-archive?

No - at least something else to begin with.
A special liker script is used when building the vdsp files for x86 - and the
linker script is ignored as such when embedded in a .o file with ar it seems.
This is not a big suprise.

The makefile magic used for the vdso part of the kernel needs a bit more coffee
than what is good for me for now...
Will look at it again later.

Thanks for the feedback.

	Sam

      reply	other threads:[~2014-02-20 17:02 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
2014-02-19  1:01     ` Alan Modra
2014-02-20 17:02       ` Sam Ravnborg [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=20140220170209.GA5103@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.