Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
From: "Noel L Yap" <yap_noel@jpmorgan.com>
To: david.karr@cacheflow.com
cc: cygwin@cygwin.com
Message-ID: <85256A79.0062C8FE.00@nyc-ntgw-n01.ny.jpmorgan.com>
Date: Thu, 28 Jun 2001 13:58:55 -0400
Subject: Re: Make: How to force a particular build order when using "-jN"
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline

I wouldn't think so.

The way to control order would be:

all: foo

foo: bar
     touch $@

bar:
     touch $@

then bar would get built before foo.

Noel


|--------+------------------------>
|        |                        |
|        |          david.karr@cac|
|        |          heflow.com    |
|        |                        |
|        |          06/28/01 11:45|
|        |          AM            |
|        |                        |
|--------+------------------------>
  >----------------------------------------------------------------------------|
  |                                                                            |
  |       To:     cygwin@cygwin.com                                            |
  |       cc:     (bcc: Noel L Yap)                                            |
  |       Subject:     Make: How to force a particular build order when using  |
  |       "-jN"                                                                |
  >----------------------------------------------------------------------------|


When in the presence of "make -jN", and with the following example, I
believe that the order of building "foo" and "bar" is indeterminate.

-------------
all: foo bar

foo:
     touch foo

bar:
     touch bar
-------------

However, is it the case that with this next example, that the order CAN be
determined, and that "foo" would be built before "bar", even in the presence
of "make -jN"?

-------------
all:: foo
all:: bar

foo:
     touch foo

bar:
     touch bar
-------------

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


This communication is for informational purposes only.  It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan Chase & Co., its
subsidiaries and affiliates.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/