All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ing.Gianfranco Morandi (LAN)" <gianfranco.morandi@euro-studio.it>
To: "Wolfgang Denk" <wd@denx.de>
Cc: "LinuxPPC" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: "mkimage" not found
Date: Fri, 5 Mar 2004 10:10:53 +0100	[thread overview]
Message-ID: <00a101c40291$c31a7120$0400a8c0@portatile> (raw)
In-Reply-To: 20040304110742.949A1C0655@atlas.denx.de


Dear Wolfgang

> Maybe your PATH ist not correct?

You are perfectly right! I didn't add the line "export
PATH=$PATH:/opt/eldk/usr/bin"  to .bashrc.
Many thanks

> > With the previous ELDK2.0 I would have generated the image with the
"make
> > pImage" command while now I suppose the command "make uImage" must be
used.
> > Is this correct?
>
> This is correct, but "make pImage" will still work, too.

unfortunately I had the following messages:

[gianfranco@home001 linux]$ make pImage
make: *** No rule to make target `pImage'.  Stop.
[gianfranco@home001 linux]$ grep -r pImage *
arch/ppc/boot/Makefile:pImage: $(MKIMAGE) images/vmlinux.gz
[gianfranco@home001 linux]$ grep -r uImage *
arch/ppc/boot/Makefile:uImage  \
arch/ppc/boot/Makefile: ln -sf vmlinux.UBoot images/uImage
arch/ppc/Makefile:BOOT_TARGETS = zImage zImage.initrd znetboot
znetboot.initrd uImage
CHANGELOG:Add support for U-Boot boot image "uImage"
[gianfranco@home001 linux]$


Should I modify BOOT_TARGET into arch/ppc/Makefile?

Best regards
Gianfranco


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-03-05  9:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-04 10:33 "mkimage" not found Ing.Gianfranco Morandi (LAN)
2004-03-04 11:07 ` Wolfgang Denk
2004-03-05  9:10   ` Ing.Gianfranco Morandi (LAN) [this message]
2004-03-05  9:19     ` Wolfgang Denk
2004-03-05 16:45     ` listmember

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='00a101c40291$c31a7120$0400a8c0@portatile' \
    --to=gianfranco.morandi@euro-studio.it \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=wd@denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.