From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from ozlabs.org ([203.10.76.45]) by bombadil.infradead.org with esmtps (Exim 4.68 #1 (Red Hat Linux)) id 1KVSOF-00022d-Ok for kexec@lists.infradead.org; Tue, 19 Aug 2008 14:40:56 +0000 From: Jeremy Kerr Subject: Re: [PATCH] Explicitly use BUILD_CC and TARGET_CC Date: Tue, 19 Aug 2008 22:40:16 +0800 References: <1219030410.884068.167991623519.1.gpush@pingu> <20080818071037.GA5029@verge.net.au> <200808181519.48759.jk@ozlabs.org> In-Reply-To: <200808181519.48759.jk@ozlabs.org> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200808192240.16919.jk@ozlabs.org> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: kexec-bounces@lists.infradead.org Errors-To: kexec-bounces+dwmw2=infradead.org@lists.infradead.org To: kexec@lists.infradead.org Cc: Simon Horman > That should be fine: we just add a rule for %.o: %.S OK, that's not going to work, because rules of the form list: pattern: prereq *require* the prereqs to be build. ie, in our case: $(PURGATORY_OBJS): %.o: %.S will require a .S for all .o files in PURGATORY_OBJS. Which is not what we want :( So, the solution left would be to override COMPILE.c, COMPILE.S and LINK.o for target and build compiles. For example: $(PURGATORY_OBJS): COMPILE.c = $(TARGET_CC) $(TARGET_CFLAGS) \ $(TARGET_CPPFLAGS) -c It's unlikely that a user is going to override COMPILE.c on the make command-line :) How does that sound? Cheers, Jeremy _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec