From: Lars Ingebrigtsen <larsi@gnus.org>
To: Tom Tromey <tom@tromey.com>
Cc: 28827@debbugs.gnu.org
Subject: bug#28827: 26.0.60; compilation mode -vs- messages from make
Date: Mon, 15 Jul 2019 10:59:25 +0200 [thread overview]
Message-ID: <874l3nvfki.fsf@mouse.gnus.org> (raw)
In-Reply-To: <87zi8utkjh.fsf@tromey.com> (Tom Tromey's message of "Fri, 13 Oct 2017 22:34:10 -0600")
Tom Tromey <tom@tromey.com> writes:
> I'm using an Emacs built from the emacs 26 branch.
> I have GNU make 4.2.1.
>
> When I compile, if I get an error, make also prints this, e.g.:
>
> make: *** [Makefile:1928: breakpoint.o] Error 1
>
>
> In the *compilation* buffer, the "*** [Makefile:" text is highlighted
> red.
>
> When I next-error, Emacs will ask me:
>
> Find this error in (default *** [Makefile): ~/gdb/build/gdb
On the trunk, I get:
callint.c:895:13: note: each undeclared identifier is reported only once for each function it appears in
Makefile:402: recipe for target 'callint.o' failed
make[1]: *** [callint.o] Error 1
and Emacs doesn't ask me for anything when next-error-ing to the file.
(This is on the trunk.) Are you still seeing this problem?
> However, this sort of error is basically never interesting, as it's not
> a bug in the Makefile; it is just make reporting which rule
> failed... but I already know which rule failed from the earlier
> messages.
>
> I think it would be an improvement if compilation mode ignored these
> messages.
Hm... well, I guess it's mostly not interesting, but I could see that
some people would find it interesting sometimes...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-07-15 8:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-14 4:34 bug#28827: 26.0.60; compilation mode -vs- messages from make Tom Tromey
2019-07-15 8:59 ` Lars Ingebrigtsen [this message]
2019-11-02 0:49 ` Stefan Kangas
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874l3nvfki.fsf@mouse.gnus.org \
--to=larsi@gnus.org \
--cc=28827@debbugs.gnu.org \
--cc=tom@tromey.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).