linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: Olaf Hering <olh@suse.de>,
	linuxppc-dev@ozlabs.org, Sam Ravnborg <sam@ravnborg.org>
Subject: Re: make -j12 all fails in uImage target
Date: Sun, 6 Feb 2005 16:50:55 -0700	[thread overview]
Message-ID: <20050206235055.GH7686@smtp.west.cox.net> (raw)
In-Reply-To: <20050206225323.GA16821@mars.ravnborg.org>

On Sun, Feb 06, 2005 at 11:53:23PM +0100, Sam Ravnborg wrote:
> On Sun, Feb 06, 2005 at 02:51:31PM -0700, Tom Rini wrote:
> > On Sun, Feb 06, 2005 at 01:40:14PM +0100, Olaf Hering wrote:
> > > 
> > > this is what I got with 2.6.11rc3:
> > > 
> > > make ARCH=ppc O=../O-2.6.11-rc3-b50-SMP -j12 all
> > > ...
> > >   LD      vmlinux
> > >   SYSMAP  System.map
> > >   SYSMAP  .tmp_System.map
> > >   OBJCOPY arch/ppc/boot/images/vmlinux.bin
> > >   HOSTCC  arch/ppc/boot/utils/addnote
> > >   HOSTCC  arch/ppc/boot/utils/mknote
> > >   HOSTCC  arch/ppc/boot/utils/mkprep
> > >   LD      arch/ppc/boot/lib/built-in.o
> > >   HOSTCC  arch/ppc/boot/utils/hack-coff
> > >   HOSTCC  arch/ppc/boot/utils/mkbugboot
> > >   OBJCOPY arch/ppc/boot/images/vmlinux.bin
> > >   GZIP    arch/ppc/boot/images/vmlinux.gz
> > > /bin/sh: line 1: arch/ppc/boot/images/vmlinux.bin: No such file or directory
> > > make[2]: *** [arch/ppc/boot/images/vmlinux.gz] Error 1
> > > make[1]: *** [uImage] Error 2
> > > make[1]: *** Waiting for unfinished jobs....
> > > 
> > > also, one time that zImage.chrp was only 570K instead of the expected
> > > 1.4M, so netboot failed. But I got no build error.
> > > Any idea what dependency is missing?
> > 
> > That is kinda odd.  My thought is that arch/ppc/boot/ just isn't fully
> > safe for -j'ing.  Sam, any ideas on how to debug this kinda problem?
> 
> The problem is that the images/ sub directory is visited before the
> prerequisites are finished.
> I have no good way to debug this - I can see it based on the Makefile and
> the output Olaf included.
> 
> Also the problem Olaf describe is just a cp of a half finished file.
> 
> 
> So the fix is to let the images/ directory depends on the rest of the
> directories.
> 
> Something like this may do the trick:
> 
> $(obj)/images: $(addprefix $(obj)/,$(subdir-y) $(bootdir-y))
> 	$(Q)$(MAKE) $(build)=$@
> 
> And then delete the assignment of images to subdir-y
> 
> 
> Another solution would be to get rid on the images/ drectory and place
> outputfiles where they are being built.

Hopefully the first works, since I really do like having all the various
images we create end up in one spot. :)

-- 
Tom Rini
http://gate.crashing.org/~trini/

  parent reply	other threads:[~2005-02-06 23:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-06 12:40 make -j12 all fails in uImage target Olaf Hering
2005-02-06 21:51 ` Tom Rini
2005-02-06 21:57   ` Olaf Hering
2005-02-06 22:53   ` Sam Ravnborg
2005-02-06 23:43     ` Benjamin Herrenschmidt
2005-02-07  5:39       ` Sam Ravnborg
2005-02-06 23:50     ` Tom Rini [this message]
2005-02-07  8:29     ` Olaf Hering
2005-02-16 15:54       ` Tom Rini
2005-05-25 21:34     ` Olaf Hering
2005-07-12 21:29 ` [PATCH] " Olaf Hering
2005-07-12 21:36   ` 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=20050206235055.GH7686@smtp.west.cox.net \
    --to=trini@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=olh@suse.de \
    --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;
as well as URLs for NNTP newsgroup(s).