From: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: Jeff Dike <jdike@addtoit.com>,
user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: uml kbuild cleanup (cross-build) - some fixes and comments
Date: Thu, 10 Feb 2005 20:11:28 +0000 [thread overview]
Message-ID: <20050210201128.GD8859@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <200502101939.23300.blaisorblade@yahoo.it>
On Thu, Feb 10, 2005 at 07:39:23PM +0100, Blaisorblade wrote:
> First, Al, thanks a lot for succeeding in solving this... I had tried a lot of
> time ago to make sure that O= worked... (I think that -j already worked,
> unless somebody re-broke it after I fixed that). Plus you fix a lot of other
> stuff.
>
> There are (at least) two bugs to fix about this patch, plus some comments:
>
> http://user-mode-linux.sourceforge.net/work/current/2.6/2.6.11-rc3-mm1/patches/cross-build
>
> 1) typo here: "objtre" should be "objtree"
>
> Index: linux-2.6.10/arch/um/kernel/Makefile
> ===================================================================
>
> @@ -50,7 +50,7 @@
> quiet_cmd_quote2 = QUOTE $@
> cmd_quote2 = sed -e '/CONFIG/{' \
> -e 's/"CONFIG"\;/""/' \
> - -e 'r $(obj)/config.tmp' \
> + -e 'r $(objtre)/config.tmp' \
Where had that come from? The patch I've done is on
ftp://ftp.linux.org.uk/pub/people/viro/UML-kbuild. I don't see that
chunk in there. The closest I can find is
-QUOTE = 'my $$config=`cat $(TOPDIR)/.config`; $$config =~ s/"/\\"/g ; $$config =~ s/\n/\\n"\n"/g ; while(<STDIN>) { $$_ =~ s/CONFIG/$$config/; print $$_ }'
+QUOTE = 'my $$config=`cat $(objtree)/.config`; $$config =~ s/"/\\"/g ; $$config =~ s/\n/\\n"\n"/g ; while(<STDIN>) { $$_ =~ s/CONFIG/$$config/; print $$_ }'
quiet_cmd_quote = QUOTE $@
cmd_quote = $(PERL) -e $(QUOTE) < $< > $@
targets += config.c
-$(obj)/config.c : $(src)/config.c.in $(TOPDIR)/.config FORCE
+$(obj)/config.c : $(src)/config.c.in $(objtree)/.config FORCE
Note that it's not -mm-based; problem with porting to -mm, maybe? Or
I might have equivalent typo in one of the older versions of patch and
it migrated...
BTW, that chunk in your patch looks bogus regardless of typos - you have
config.tmp in clean-files, so it'd better be in arch/um/kernel, not in
the root...
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-02-10 20:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-10 18:39 [uml-devel] uml kbuild cleanup (cross-build) - some fixes and comments Blaisorblade
2005-02-10 19:04 ` [uml-devel] " Al Viro
2005-02-10 19:16 ` Blaisorblade
2005-02-10 20:16 ` Al Viro
2005-02-10 20:11 ` Al Viro [this message]
2005-02-10 20:19 ` Blaisorblade
2005-02-10 23:11 ` Jeff Dike
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=20050210201128.GD8859@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=blaisorblade@yahoo.it \
--cc=jdike@addtoit.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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