Re: CYGWIN withholds error message when trying to run 64-bit binary on 32-bit PC

2011-04-29 Thread John Ottusch
> > THe problem is that the Win32 error code ERROR_EXE_MACHINE_TYPE_MISMATCH > isn't mapped to a POSIX errno. Thus it's converted to the default EACCES. > I checked in a patch to CVS which maps the error code to ENOEXEC. > > Corinna > Mucho thanko. I'll look forward to the next CYGWIN rele

Re: CYGWIN withholds error message when trying to run 64-bit binary on 32-bit PC

2011-04-29 Thread Corinna Vinschen
On Apr 29 17:52, John Ottusch wrote: > 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

CYGWIN withholds error message when trying to run 64-bit binary on 32-bit PC

2011-04-29 Thread John Ottusch
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