From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Reuben Thomas <rrt@sc3d.org>
Cc: 8715@debbugs.gnu.org
Subject: bug#8715: 23.3.50; Use GNU, not Windows syntax in example code in flymake manual
Date: Fri, 15 Jul 2011 16:01:05 +0200 [thread overview]
Message-ID: <m34o2n8wym.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87aaef8zlt.fsf@sc3d.org> (Reuben Thomas's message of "Sat, 21 May 2011 23:20:46 +0100")
Reuben Thomas <rrt@sc3d.org> writes:
> The flymake manual contains the following handy sample make rule:
>
> check-syntax:
> gcc -o nul -S ${CHK_SOURCES}
>
> But using “nul” is useful on Windows (it works on GNU too, but creates
> an output file, and the point of the rule is to avoid doing that).
> Hence, use the GNU syntax:
>
> check-syntax:
> gcc -o /dev/null -S ${CHK_SOURCES}
I've now done this change in Emacs 24.
> A further suggestion is to suggest the following rule for automake users:
>
> check-syntax:
> $(COMPILE) -o /dev/null -S $(CHK_SOURCES)
>
> As this adds compiler flags which may be needed, for example to find
> include files. A further reason this is handy is that the undocumented
> make target dumpvars which is used by
> flymake-get-project-include-dirs-imp cannot easily be implemented in
> automake (at least, my attempt ended in tears, since it required the use
> of a GNU make construct, which is not permitted in automake). The above
> check-syntax target makes this unnecessary.
I know next to nothing about flymake, so I'm afraid I'm not a good judge
of this change, though. Anybody?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2011-07-15 14:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-21 22:20 bug#8715: 23.3.50; Use GNU, not Windows syntax in example code in flymake manual Reuben Thomas
2011-07-15 14:01 ` Lars Magne Ingebrigtsen [this message]
2012-03-10 4:10 ` Chong Yidong
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=m34o2n8wym.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=8715@debbugs.gnu.org \
--cc=rrt@sc3d.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.