This is the mail archive of the
mailing list for the Cygwin project.
Re: Cygwin exe magic does not understand .com extension? [or .exe sometimes]
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 5 Nov 2013 00:24:05 -0500
- Subject: Re: Cygwin exe magic does not understand .com extension? [or .exe sometimes]
- Authentication-results: sourceware.org; auth=none
- References: <3310368726 dot 20131105025244 at mtu-net dot ru> <20131105035821 dot GB3059 at ednor dot casa dot cgf dot cx> <20131105044434 dot GA23590 at raf dot org>
- Reply-to: cygwin at cygwin dot com
On Tue, Nov 05, 2013 at 03:44:35PM +1100, <someone who insists on putting "cygwin" in their email address without using their real name> wrote:
>Christopher Faylor wrote:
>> On Tue, Nov 05, 2013 at 02:52:44AM +0400, Andrey Repin wrote:
>> >Greetings, All!
>> >$ mode<Tab>
>> >mode.com modemui.dll modex.dll
>> That would be /bin/sh exe magic from the looks of it. It is probably
>> just trying to find anything with an executable bit set, just like on
>> >$ mode
>> >bash: mode: command not found
>> >Now, I see two issues.
>> >First, it is that it see .dll files as executables. Which is true in essence,
>> >but rather suspicious, as .dll files are normally not directly executable.
>> >Would really like an explanation for this behavior.
>> >Second, is that it actually see mode.com, but unable to execute it.
>> It's likely that "mode.com" would execute it.
>this sounds like the problem i posted about the other day that trying to
>execute gcc doesn't work but gcc.exe does. it's a pity. i wish someone had
>an explanation why it happens with some programs like gcc (and mode) but not
>others. a solution would be even better. but i've given up trying to compile
>python modules so i can live with the failure.
No, this isn't the same thing at all. It is perfectly understandable
why you'd need to type 'mode.com'. The only reason why you'd need to
add .exe to gcc is if you either have a gcc without an extension
somewhere or you aren't using a cygwin program to start gcc.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple