This is the mail archive of the
mailing list for the Cygwin project.
Re: gcc writing to /dev/null actually writes to /dev/null.exe
- From: "Larry Hall (Cygwin)" <reply-to-list-only-lh at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 09 Sep 2013 13:09:16 -0400
- Subject: Re: gcc writing to /dev/null actually writes to /dev/null.exe
- Authentication-results: sourceware.org; auth=none
- References: <CAJty3Zx2dRRsp31kwN6OGM-mJkGO6YsVVLHg9Y2JDsjH+0op7Q at mail dot gmail dot com>
- Reply-to: cygwin at cygwin dot com
On 9/9/2013 12:24 PM, Adam Kellas wrote:
Is this a bug which is fixable in Cygwin or just something to be lived with?
% gcc -o /dev/null devnull.c
% ls -ld /dev/null*
crw-rw-rw- 1 dboyce Domain Users 1, 3 Sep 9 09:14 /dev/null
-rwxrwxr-x+ 1 dboyce Domain Users 53827 Sep 9 09:14 /dev/null.exe
% file /dev/null.exe
/dev/null.exe: PE32 executable (console) Intel 80386, for MS Windows
I'm aware of the .exe back story but this should be a special case, I think.
I can't imagine that this corner case is worth adding overhead to the
transparent exe handling code. It also would open the door to arguments
to support other special cases. That said, the final say goes to the
persons who generate a patch and those who review it.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple