From: Kevin Ryde <user42@zip.com.au>
Subject: automake 1.10 vs guile-func-name-check
Date: Sun, 03 Dec 2006 10:37:35 +1100 [thread overview]
Message-ID: <87d5717tts.fsf@zip.com.au> (raw)
As mentioned on bug-guile, I switched to automake 1.10 in the
top-level makefile. Among the new complaints is the bogosity of this
line in libguile/Makefile.am
-(test -n "${AWK+set}" || AWK="@AWK@"; ${AWK} -f ./guile-func-name-check $<)
I expect it's meant to be "$${AWK:+set}" for a start, but even so I
don't think it has the intended effect. AC_PROG_AWK puts an AWK=awk
in the generated Makefile, which will override a setting of $AWK in
the environment, which the "test" is apparently looking at.
I changed it to simply
-$(AWK) -f ./guile-func-name-check $<
which I think is right, unless anyone can explain the intention of the
old bit. You can still force to a particular awk with
make AWK=my-groovy-awk
and that overrides other uses of $(AWK) like in the TAGS rule and
stuff.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2006-12-02 23:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-02 23:37 Kevin Ryde [this message]
2006-12-14 20:16 ` automake 1.10 vs guile-func-name-check Neil Jerram
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d5717tts.fsf@zip.com.au \
--to=user42@zip.com.au \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).