[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: MinGW build broken with O_CLOEXEC undeclared

From: Paul Eggert
Subject: Re: MinGW build broken with O_CLOEXEC undeclared
Date: Sun, 8 Mar 2020 03:08:05 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1

On 3/8/20 1:34 AM, martin rudalics wrote:
 > Did the MinGW port formerly compile open.c?

No, AFAICT (on the release branch it doesn't).

It's not an issue of the master vs the release branch; it's an issue of before and after commit 5d4cf1fef85bc24bc4cd9705ebb14150263ad707, which added the nofollow flag to set-file-times.

If not, why is the MinGW port compiling open.c now?

How would I find out?

Find out why the 'configure' script is executing 'REPLACE_OPEN=1' now, when it didn't do it before that commit. You may need to put some debugging commands into it, e.g., 'echo "got to here" >>/tmp/log'.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]