All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Limpach <christian.limpach@gmail.com>
To: Hollis Blanchard <hollisb@us.ibm.com>
Cc: xen-devel@lists.sourceforge.net,
	Jerone Young <jyoung5@us.ibm.com>,
	iap10@cl.cam.ac.uk, kaf24@cl.cam.ac.uk
Subject: Re: [PATCH] tools top level makefile cleanup
Date: Wed, 23 Mar 2005 22:35:11 +0000	[thread overview]
Message-ID: <3d8eece205032314357ea23998@mail.gmail.com> (raw)
In-Reply-To: <200503231517.53622.hollisb@us.ibm.com>

On Wed, 23 Mar 2005 15:17:53 -0600, Hollis Blanchard <hollisb@us.ibm.com> wrote:
> On Wednesday 23 March 2005 15:11, Christian Limpach wrote:
> > At least you didn't try to go down the insane "try to make everything
> > build in parallel" road, it might work for the tools but you need to
> > be careful to make sure that targets which other targets depend on get
> > built first.  None of the fancy Makefile tricks which other people
> > have posted seem to take this into account :-(
> 
> That is explicitly described in the GNU make manual; see the "foo: baz" line
> here:
> http://www.gnu.org/software/make/manual/html_chapter/make_4.html#SEC41
> 
> So that seems to be a very small problem...

I know how Makefile dependencies work, thank you.  The point I was
trying to make was that all the sophisticated Makefile solutions to
support parallel builds are nice, but they are useless to us unless
someone provides a complete patch which includes correct dependency
handling.

I like the original patch (except for the small check install
oversight), since it's simple and I can convince myself that it is
correct.  I'm not sure it is needed right now though.  One example
would be that it has the potential to break patches applied when
building packages.

    christian


-------------------------------------------------------
This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005
Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows
Embedded(r) & Windows Mobile(tm) platforms, applications & content.  Register
by 3/29 & save $300 http://ads.osdn.com/?ad_id=6883&alloc_id=15149&op=click

  reply	other threads:[~2005-03-23 22:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-22 21:10 [PATCH] tools top level makefile cleanup Jerone Young
2005-03-22 21:33 ` Adam Heath
2005-03-22 21:46   ` Jerone Young
2005-03-23 18:01     ` Adam Heath
2005-03-23 20:15       ` Hollis Blanchard
2005-03-23 20:48         ` Anthony Liguori
2005-03-23 20:57           ` Hollis Blanchard
2005-03-24 20:13             ` Adam Heath
2005-03-24 20:08           ` Adam Heath
2005-03-24 20:07         ` Adam Heath
2005-03-23 21:11 ` Christian Limpach
2005-03-23 21:17   ` Hollis Blanchard
2005-03-23 22:35     ` Christian Limpach [this message]
2005-03-24 20:11   ` Adam Heath
  -- strict thread matches above, loose matches on Subject: below --
2005-03-22 22:18 Nakajima, Jun
2005-03-22 22:14 ` Jerone Young
2005-03-22 22:25 Nakajima, Jun
     [not found] <mailman.1111526259.18440@unix-os.sc.intel.com>
     [not found] ` <4240A373.7080406@intel.com>
2005-03-23 20:41   ` Jerone Young
     [not found] <488257396@toto.iv>
2005-03-24 14:56 ` Jimi Xenidis

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=3d8eece205032314357ea23998@mail.gmail.com \
    --to=christian.limpach@gmail.com \
    --cc=Christian.Limpach@cl.cam.ac.uk \
    --cc=hollisb@us.ibm.com \
    --cc=iap10@cl.cam.ac.uk \
    --cc=jyoung5@us.ibm.com \
    --cc=kaf24@cl.cam.ac.uk \
    --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.