bug#70716: closed (flymake-cc creates `-.o` files)

[GNU bug Tracking System]

Your message dated Wed, 28 Aug 2024 19:50:00 +0200
with message-id <915DA9CD-3EB2-46C4-8FA2-B9ED923E881B@gmail.com>
and subject line Re: bug#70716: flymake-cc creates `-.o` files
has caused the debbugs.gnu.org bug report #70716,
regarding flymake-cc creates `-.o` files
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
70716: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=70716
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems

--- Begin Message --- Subject: flymake-cc creates `-.o` files Date: Thu, 2 May 2024 15:10:18 +0200

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

flymake-cc-null-output.diff
Description: Binary data

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#70716: flymake-cc creates `-.o` files
>
>
>
>
> Date: 
>
> Wed, 28 Aug 2024 19:50:00 +0200
>
>
>
>
> 28 aug. 2024 kl. 19.01 skrev sbaugh@catern.com:
>
> > check-syntax:
> >       gcc -o /dev/null -S ${CHK_SOURCES} || true
> > 
> > So it seems like it would be better to add this -o /dev/null in your
> > Makefile.
>
> Actually not my Makefile but that of flymake-tests.
> Anyway, now done on master, thank you!
>
>
>
> --- End Message ---