From: Andreas Schwab <schwab@suse.de>
To: Wolfgang Denk <wd@denx.de>
Cc: Andrew Morton <akpm@osdl.org>,
linuxppc-dev@ozlabs.org, paulus@au.ibm.com
Subject: Re: [PATCH v2] powerpc: Do not fail build if mkimage is not available
Date: Thu, 27 Dec 2007 11:17:42 +0100 [thread overview]
Message-ID: <jetzm4jvax.fsf@sykes.suse.de> (raw)
In-Reply-To: <20071227101404.2C05F2405E@gemini.denx.de> (Wolfgang Denk's message of "Thu\, 27 Dec 2007 11\:14\:04 +0100")
Wolfgang Denk <wd@denx.de> writes:
> In message <200712261708.51432.mb@bu3sch.de> you wrote:
>> On Wednesday 26 December 2007 17:03:43 Andreas Schwab wrote:
>> > Michael Buesch <mb@bu3sch.de> writes:
>> >
>> > > + set +e
>> > > mkimage -A ppc -O linux -T kernel -C gzip -a 00000000 -e 00000000 \
>> > > $uboot_version -d "$vmz" "$ofile"
>> > > + [ $? -eq 0 ] || exit 0
>> > > + set -e
>> >
>> > mkimage ... || exit 0
>>
>> Could you PLEASE increase your verbosity?
>> Why is mkimage || exit 0 any better than my test?
>
> Because it works, while your's doesn't.
>
> Make runs each command in a new shell.
This is a shell script, not a makefile.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2007-12-27 10:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-26 15:55 [PATCH v2] powerpc: Do not fail build if mkimage is not available Michael Buesch
2007-12-26 16:03 ` Andreas Schwab
2007-12-26 16:08 ` Michael Buesch
2007-12-26 16:19 ` Andreas Schwab
2007-12-27 10:14 ` Wolfgang Denk
2007-12-27 10:17 ` Andreas Schwab [this message]
2007-12-27 18:13 ` Michael Buesch
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=jetzm4jvax.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=akpm@osdl.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@au.ibm.com \
--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 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).