From: Eli Zaretskii <eliz@is.elta.co.il>
To: "H . J . Lu" <hjl@lucon.org>
Cc: "J.T. Conklin" <jtc@redback.com>,
Andrew Cagney <ac131313@cygnus.com>,
gdb-patches@sourceware.cygnus.com,
"Paul D. Smith" <psmith@gnu.org>
Subject: Re: [RFA]: simulator build failures with parallel make
Date: Sun, 15 Apr 2001 22:53:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1010416094820.28005E-100000@is> (raw)
In-Reply-To: <20010415135646.A25615@lucon.org>
On Sun, 15 Apr 2001, H . J . Lu wrote:
> > foo.tab.c foo.tab.h: foo-stamp
> >
> > foo-stamp: foo.y
> > $(YACC) -b foo -p foo -d $?
> > touch $@
> >
> > So what exactly is your complaint about my patch.
> >
>
> That is a bug in Makefile and that is why we have ylwrap. See how it is
> done in ld/Makefile.*, binutils/Makefile.* and gas/Makefile.*.
With GNU Make, you can avoid the problem with pattern rules (which
specifically target cases like Yacc and Bison).
IMVHO, ylwrap is a kludge. It might be okay to have users of non-GNU
Make to need it, but GNU Make should have a cleaner feature for when
a command produces several target files in a single run. (Pattern rules
only work well when all the files created by the program have the same
stem; if not, you need to define your patterns ``creatively''.)
prev parent reply other threads:[~2001-04-15 22:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-27 12:26 J.T. Conklin
2001-04-06 11:08 ` Andrew Cagney
2001-04-06 11:30 ` Frank Ch. Eigler
2001-04-08 23:28 ` Eli Zaretskii
2001-04-15 12:54 ` J.T. Conklin
2001-04-15 13:13 ` H . J . Lu
2001-04-15 13:47 ` J.T. Conklin
2001-04-15 13:56 ` H . J . Lu
2001-04-15 22:53 ` Eli Zaretskii [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=Pine.SUN.3.91.1010416094820.28005E-100000@is \
--to=eliz@is.elta.co.il \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sourceware.cygnus.com \
--cc=hjl@lucon.org \
--cc=jtc@redback.com \
--cc=psmith@gnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox