From: Jerone Young <jyoung5@us.ibm.com>
To: Adam Heath <doogie@brainfood.com>
Cc: xen-devel <xen-devel@lists.sourceforge.net>
Subject: Re: [PATCH][RESUBMIT] tools top level makefile cleanup
Date: Fri, 25 Mar 2005 14:28:04 -0600 [thread overview]
Message-ID: <1111782485.11028.8.camel@thinkpad> (raw)
In-Reply-To: <Pine.LNX.4.58.0503251420180.1720@gradall.private.brainfood.com>
That can easily be fixed when put in the tree. The main point is to exit
with a non zero value. True by exiting with -1 can't get the negative
exit code from the shell (you would get 255). But still bahaviors the
same way if $? != 0 then we know something is wrong.
On Fri, 2005-03-25 at 14:21 -0600, Adam Heath wrote:
> On Fri, 25 Mar 2005, Adam Heath wrote:
>
> > On Fri, 25 Mar 2005, Jerone Young wrote:
> >
> > > +all: check
> > > + @for subdir in $(SUBDIRS); do \
> > > + $(MAKE) -C $$subdir $@ || exit -1; \
> > > + done
> >
> > How is this a valid makefile? Where's the tab?
>
> Please use "@set -e; for ...", and remove the "|| exit -1".
>
> Besides, exit -1 is poor, it s/b a positive number. It's not really possible
> to exit with a negative value.
>
--
Jerone Young
IBM Linux Technology Center
jyoung5@us.ibm.com
512-838-1157 (T/L: 678-1157)
-------------------------------------------------------
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
prev parent reply other threads:[~2005-03-25 20:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-25 17:07 [PATCH][RESUBMIT] tools top level makefile cleanup Jerone Young
2005-03-25 18:38 ` Adam Heath
2005-03-25 18:51 ` Jerone Young
2005-03-25 19:04 ` Anthony Liguori
2005-03-25 19:12 ` Adam Heath
2005-03-25 18:58 ` Jerone Young
2005-03-25 20:21 ` Adam Heath
2005-03-25 20:28 ` Jerone Young [this message]
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=1111782485.11028.8.camel@thinkpad \
--to=jyoung5@us.ibm.com \
--cc=doogie@brainfood.com \
--cc=xen-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 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.