From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: zImage: Skip relinking if nothing changes
Date: Fri, 12 Aug 2011 21:55:20 +0100 [thread overview]
Message-ID: <20110812205520.GL4775@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CACqU3MUq5M-XPOxV=8GKyEzjEzpmdeaF+mGrXJrK+ZZxa4SdeQ@mail.gmail.com>
On Fri, Aug 12, 2011 at 04:48:12PM -0400, Arnaud Lacombe wrote:
> You should be able to avoid the extra copy altogether by doing something ala:
>
> $(obj)/lib1funcs.o: $(srctree)/arch/arm/lib/lib1funcs.S
> $(call cmd,as_o_S)
>
> note that I also remove the $(SRCARCH), as there is no other
> `arch/*/lib/lib1funcs.S' than `arch/arm/lib/lib1funcs.S'
We tried such things, but it results in kbuild arguing over building
lib1funcs.S in arch/arm/lib and arch/arm/boot/compressed. You end up
with it rebuilding the arch/arm/lib one, followed by a rebuild of the
arch/arm/boot/compressed one.
We've ended up with what we have because its about the only way to get
kbuild to behave.
next prev parent reply other threads:[~2011-08-12 20:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 17:46 Relinking zImage when nothing changes Stephen Boyd
2011-08-12 18:02 ` Sam Ravnborg
2011-08-12 18:12 ` Stephen Boyd
2011-08-12 18:34 ` Sam Ravnborg
2011-08-12 18:52 ` Stephen Boyd
2011-08-12 19:00 ` [PATCH] ARM: zImage: Skip relinking if " Stephen Boyd
2011-08-12 20:48 ` Arnaud Lacombe
2011-08-12 20:55 ` Russell King - ARM Linux [this message]
2011-08-12 21:41 ` Arnaud Lacombe
2011-08-12 22:03 ` Sam Ravnborg
2011-08-12 22:17 ` Arnaud Lacombe
2011-08-13 6:34 ` Sam Ravnborg
2011-08-13 16:02 ` Arnaud Lacombe
2011-08-12 22:32 ` Arnaud Lacombe
2011-08-18 3:44 ` Nicolas Pitre
2011-08-18 18:03 ` Arnaud Lacombe
2011-08-18 19:31 ` Russell King - ARM Linux
2011-08-18 22:25 ` Troy Kisky
2011-08-18 22:38 ` Arnaud Lacombe
2011-08-12 20:20 ` Relinking zImage when " Arnaud Lacombe
2011-08-12 20:24 ` Sam Ravnborg
2011-08-12 20:31 ` Arnaud Lacombe
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=20110812205520.GL4775@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).