From: Olaf Hering <olh@suse.de>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] generate COFF zImage in arch/powerpc/boot
Date: Sat, 19 Nov 2005 09:46:54 +0100 [thread overview]
Message-ID: <20051119084654.GA29731@suse.de> (raw)
In-Reply-To: <17278.40894.898159.724090@cargo.ozlabs.ibm.com>
On Sat, Nov 19, Paul Mackeras wrote:
> There is still something I haven't got right: if you do make -j3, it
> does this sort of thing:
>
> STRIP vmlinux.strip
> STRIP vmlinux.strip
> GZIP arch/powerpc/boot/kernel-vmlinux.strip.gz
> GZIP arch/powerpc/boot/kernel-vmlinux.strip.gz
> BOOTCC arch/powerpc/boot/kernel-vmlinux.strip.o
> BOOTCC arch/powerpc/boot/kernel-vmlinux.strip.o
> mv: cannot stat `arch/powerpc/boot/.kernel-vmlinux.strip.o.tmp': No such file or directory
> make[2]: *** [arch/powerpc/boot/kernel-vmlinux.strip.o] Error 1
> make[1]: *** [zImage] Error 2
>
> I have no idea why it tries to make those things twice in parallel.
> It doesn't do that for vmlinux.
I think this comes from the targets evaluation. Maybe strip needs to be
some sort of serialization:
cmd_stripvm = $(STRIP) -s -R .comment $< -o $@.$$$$ && mv -v $@.$$$$ $@
gzip is also called twice, use the mygzip rule from
arch/ppc/boot/images/Makefile
--
short story of a lazy sysadmin:
alias appserv=wotan
next prev parent reply other threads:[~2005-11-19 8:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 6:06 [PATCH] generate COFF zImage in arch/powerpc/boot Paul Mackerras
2005-11-18 7:51 ` Olaf Hering
2005-11-18 22:13 ` Olaf Hering
2005-11-18 23:16 ` Olaf Hering
2005-11-19 3:45 ` Paul Mackerras
2005-11-19 8:46 ` Olaf Hering [this message]
2005-11-19 9:12 ` Olaf Hering
2005-11-19 10:29 ` Olaf Hering
2005-11-19 17:29 ` Olaf Hering
2005-11-19 20:47 ` Olaf Hering
2005-11-23 20:21 ` Olaf Hering
2005-11-23 22:35 ` Paul Mackerras
2005-11-23 22:38 ` Olaf Hering
2005-11-23 22:58 ` Olaf Hering
2005-11-23 23:06 ` Paul Mackerras
2005-12-10 18:31 ` Olaf Hering
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=20051119084654.GA29731@suse.de \
--to=olh@suse.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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).