From: "H. Peter Anvin" <hpa@zytor.com>
To: Keith Owens <kaos@ocs.com.au>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
linux-kernel@vger.kernel.org, akpm@osdl.org,
mm-commits@vger.kernel.org
Subject: Re: + git-klibc-mktemp-fix.patch added to -mm tree
Date: Mon, 10 Apr 2006 07:45:02 -0700 [thread overview]
Message-ID: <443A6F6E.7060304@zytor.com> (raw)
In-Reply-To: <14836.1144654413@kao2.melbourne.sgi.com>
Keith Owens wrote:
> "H. Peter Anvin" (on Sat, 08 Apr 2006 13:27:06 -0700) wrote:
>> Either which way; I have a better fix for the bison issue (this all has
>> to do with the fact that make's handling of tools that output more than
>> one file at a time is at the very best insane)
>
> Hit the same problem back in the 2.5 kbuild days, and worked around it
> with some dummy dependency rules. Like this one for bison/yacc.
>
> side_effect(aicasm_gram.tab.h aicasm_gram.tab.c)
>
> which expands to
>
> $(objtree)/aicasm_gram.tab.h: $objtree/aicasm_gram.tab.c
> @/bin/true
>
> That forces make to wait until aicasm_gram.tab.c is built before using
> aicasm_gram.tab.h, and allows the following code to depend on either
> aicasm_gram.tab.h or aicasm_gram.tab.c without any races. The command
> should not get executed, but you still need a command to keep make
> happy.
A better way to do it for something like yacc/bison is to use a pattern
rule. Having two things on the LHS means different things for explicit
and for pattern rules!
-hpa
next prev parent reply other threads:[~2006-04-10 14:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200604080707.k38778VV023208@shell0.pdx.osdl.net>
2006-04-08 20:14 ` + git-klibc-mktemp-fix.patch added to -mm tree Sam Ravnborg
2006-04-08 20:27 ` H. Peter Anvin
2006-04-09 5:33 ` Herbert Xu
2006-04-10 7:33 ` Keith Owens
2006-04-10 14:45 ` H. Peter Anvin [this message]
[not found] <5Zs4F-ba-13@gated-at.bofh.it>
[not found] ` <5Zs4F-ba-11@gated-at.bofh.it>
2006-04-08 23:34 ` Bodo Eggert
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=443A6F6E.7060304@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@osdl.org \
--cc=herbert@gondor.apana.org.au \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=sam@ravnborg.org \
/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.