From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>, sbaugh@catern.com
Cc: mattias.engdegard@gmail.com, joaotavora@gmail.com, 70716@debbugs.gnu.org
Subject: bug#70716: flymake-cc creates `-.o` files
Date: Sat, 20 Jul 2024 13:10:52 +0300 [thread overview]
Message-ID: <86v810cr0z.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmmgN8SG84ZoLnUf678tx-UywRRBU1N9XBYa9fH+ZneN+g@mail.gmail.com> (message from Stefan Kangas on Sat, 29 Jun 2024 22:45:50 -0700)
Ping! Spencer, would you please chime in?
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Sat, 29 Jun 2024 22:45:50 -0700
> Cc: João Távora <joaotavora@gmail.com>, sbaugh@catern.com,
> mattias.engdegard@gmail.com, 70716@debbugs.gnu.org
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> Cc: 70716@debbugs.gnu.org
> >> From: João Távora <joaotavora@gmail.com>
> >> Date: Thu, 2 May 2024 14:13:49 +0100
> >>
> >> On Thu, May 2, 2024 at 2:10 PM Mattias Engdegård <mattias.engdegard@gmail.com> wrote:
> >>
> >> `flymake-cc-use-special-make-target`, the standard value for `flymake-cc-command`, generates a
> >> command like
> >>
> >> make check-syntax CHK_SOURCES="-x c -c -"
> >>
> >> which causes the compiler (at least Clang) to create the file `-.o` that is never cleaned up and whose
> >> name is mysterious and awkward to remove.
> >>
> >> What about the patch below?
> >>
> >>
> >> Copying in Spencer Baugh, the new Flymake maintainer.
> >
> > Spencer, any comments or suggestions or patches?
> >
> > Thanks.
>
> Ping.
>
next prev parent reply other threads:[~2024-07-20 10:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 13:10 bug#70716: flymake-cc creates `-.o` files Mattias Engdegård
2024-05-02 13:13 ` João Távora
2024-05-02 14:00 ` Mattias Engdegård
2024-05-04 11:38 ` Eli Zaretskii
2024-05-18 8:33 ` Eli Zaretskii
2024-05-18 8:28 ` Eli Zaretskii
2024-06-30 5:45 ` Stefan Kangas
2024-07-20 10:10 ` Eli Zaretskii [this message]
2024-08-04 7:55 ` Eli Zaretskii
2024-08-17 8:22 ` Eli Zaretskii
2024-08-28 17:01 ` Spencer Baugh
2024-08-28 17:01 ` sbaugh
2024-08-28 17:50 ` Mattias Engdegård
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=86v810cr0z.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=70716@debbugs.gnu.org \
--cc=joaotavora@gmail.com \
--cc=mattias.engdegard@gmail.com \
--cc=sbaugh@catern.com \
--cc=stefankangas@gmail.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 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.