X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.9 required=5.0	tests=BAYES_00,FREEMAIL_FROM,SPF_HELO_PASS,T_RP_MATCHES_RCVD,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: John Ottusch <ncokwqc02 AT sneakemail DOT com>
Subject: CYGWIN withholds error message when trying to run  64-bit binary on 32-bit PC
Date: Fri, 29 Apr 2011 17:52:26 +0000 (UTC)
Lines: 28
Message-ID: <loom.20110429T192743-326@post.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
User-Agent: Loom/3.14 (http://gmane.org/)
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

I have a Windows console application that I build in both 32-bit and 64-bit
versions. They both have the same name (fsr.exe).

The 32-bit version runs from a CYGWIN bash shell console window on a 32-bit PC
and a 64-bit PC. The 64-bit version runs from a Cygwin bash shell console window
only on a 64-bit PC.

If a user mistakenly runs the 64-bit version from a CYGWIN bash shell console
window on a 32-bit Windows PC he gets this message:

bash: ./fsr.exe: Permission denied

That's not very revealing.

On the other hand, if he launches the same command from a CMD console window on
the same 32-bit Windows PC, he gets this back:

This version of fsr.exe is not compatible with the version of Windows you're
running. Check your computer's system information to see whether you need a x86
(32-bit) or x64 (64-bit) version of the program, and then contact the software
publisher.

The second result is closer to what I was hoping for.

So my question is this: Why isn't CYGWIN responding with the more helpful error
message and is there anything I can do to make it respond that way instead?

jjo


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple