unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Tom Tromey <tom@tromey.com>, 28827@debbugs.gnu.org
Subject: bug#28827: 26.0.60; compilation mode -vs- messages from make
Date: Sat, 02 Nov 2019 01:49:56 +0100	[thread overview]
Message-ID: <87r22rt83v.fsf@marxist.se> (raw)
In-Reply-To: <874l3nvfki.fsf@mouse.gnus.org> (Lars Ingebrigtsen's message of "Mon, 15 Jul 2019 10:59:25 +0200")

tags 28827 + unreproducible
close 28827
thanks

Lars Ingebrigtsen <larsi@gnus.org> writes:

> 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?

More information was requested, but none was given within 15 weeks, so
I'm closing this bug as unreproducible.

If this is still an issue, please reopen the bug report.

Best regards,
Stefan Kangas





      reply	other threads:[~2019-11-02  0:49 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
2019-11-02  0:49   ` Stefan Kangas [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

  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=87r22rt83v.fsf@marxist.se \
    --to=stefan@marxist.se \
    --cc=28827@debbugs.gnu.org \
    --cc=larsi@gnus.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).