From: Michael Elizabeth Chastain <mec@shout.net>
To: bjh21@cam.ac.uk, gdb-patches@sources.redhat.com
Subject: Re: sim/arm/Makefile.in fix for non-GNU make
Date: Tue, 06 Nov 2001 10:30:00 -0000 [thread overview]
Message-ID: <200111151716.LAA21357@duracef.shout.net> (raw)
Ben Harris writes:
> sim/arm/Makefile.in currently uses $< in a non-implicit rule. This
> doesn't work with non-GNU makes (at least NetBSD's one) since $< isn't set
> for non-implicit rules.
I got curious, so I checked the Single Unix Spec for make:
http://www.opengroup.org/onlinepubs/007908799/xcu/make.html
It says:
$<
In an inference rule, $< evaluates to the filename whose
existence allowed the inference rule to be chosen for the
target. In the .DEFAULT rule, the $< macro evaluates to the
current target name. The $< macro is evaluated only for
inference rules. For example, in the .c.a inference rule, $<
represents the prerequisite .c file.
So I think this is a good patch.
My two cents,
Michael C
next reply other threads:[~2001-11-15 17:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-06 10:30 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-06 10:04 Ben Harris
2001-11-06 20:26 ` Andrew Cagney
2001-11-06 9:03 Ben Harris
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=200111151716.LAA21357@duracef.shout.net \
--to=mec@shout.net \
--cc=bjh21@cam.ac.uk \
--cc=gdb-patches@sources.redhat.com \
/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