From: Tom Rini <trini@kernel.crashing.org>
To: Roland Dreier <roland@topspin.com>
Cc: sam@ravnborg.org, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH/take 2] ppc: fix build with O=$(output_dir)
Date: Tue, 19 Oct 2004 11:29:28 -0700 [thread overview]
Message-ID: <20041019182928.GA12544@smtp.west.cox.net> (raw)
In-Reply-To: <521xfua835.fsf_-_@topspin.com>
On Tue, Oct 19, 2004 at 11:14:38AM -0700, Roland Dreier wrote:
> Subject: [PATCH/take 2] ppc: fix build with O=$(output_dir)
>
> OK, here's a patch that builds a separate copy for arch/ppc/boot/lib.
>
> Recent changes to arch/ppc/boot/lib/Makefile cause
>
> CC arch/ppc/boot/lib/../../../../lib/zlib_inflate/infblock.o
> Assembler messages:
> FATAL: can't create arch/ppc/boot/lib/../../../../lib/zlib_inflate/infblock.o: No such file or directory
>
> when building a ppc kernel using O=$(output_dir) with CONFIG_ZLIB_INFLATE=n,
> because the $(output_dir)/lib/zlib_inflate directory doesn't get created.
>
> This patch, which uses the lib/zlib_inflate sources to build objects
> in the arch/ppc/boot/lib/directory, is one fix for the problem.
This misses the bit to invoke the checker as well (when I first thought
this up I poked Al Viro about the general question of checker on boot
code, and he wanted it, so...). And having 2 'magic' rules not just 1
is why I don't like this too much and was hoping Sam would have some
idea of a good fix.
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2004-10-19 18:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-19 6:48 [PATCH] ppc: fix build with O=$(output_dir) Roland Dreier
2004-10-19 16:44 ` Tom Rini
2004-10-19 18:14 ` [PATCH/take 2] " Roland Dreier
2004-10-19 18:29 ` Tom Rini [this message]
2004-10-19 18:58 ` Roland Dreier
2004-10-26 22:33 ` Sam Ravnborg
2004-10-31 22:39 ` Sam Ravnborg
2004-10-31 21:53 ` Tom Rini
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=20041019182928.GA12544@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@topspin.com \
--cc=sam@ravnborg.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