Re: [PATCH] configure: $(CC) -o /dev/null when output not run

Subject: Re: [PATCH] configure: $(CC) -o /dev/null when output not run

Date: Sun, 23 May 2021 18:12:58 +0300

To: David Bremner,


From: Tomi Ollila

On Sat, May 22 2021, David Bremner wrote:

> Tomi Ollila <> writes:
>> When C compilation is used just to see whether compilation
>> succeeds, there is no need to write any output file.
>> Some compilations in configure already did this.
>> Now also rm -f lines are used more consistently.
>> While at it reformatted code that prints
> no objection in principle, but has anyone tried a compiler other than
> gcc to make sure it doesn't puke when writing to /dev/null. Not sure
> why it would, but...

I gave it some thought and was sure there would be no such case...

But now that I tested with 'zig cc' -- it apparently tries to remove
the target file before recreating and fails with accessDenied if cannot
(or, hopefully it just checks permissions, as removing /dev/null as
root would be nasty...)

Too bad, I had some plans that this change would have helped but...

notmuch mailing list --
To unsubscribe send an email to