X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,RP_MATCHES_RCVD
X-Spam-Check-By:	sourceware.org
X-DKIM:	Sendmail DKIM Filter v2.8.3 mux1.uit.no pA1AOVTV005261
From:	=?utf-8?B?RWR2YXJkc2VuIEvDpXJl?= <kare DOT edvardsen AT uit DOT no>
To:	"cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject:	cannot execute binary file
Date:	Tue, 1 Nov 2011 10:24:31 +0000
Message-ID:	<1320143047.5480.78.camel@kare-desktop>
MIME-Version:	1.0
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
X-MIME-Autoconverted:	from base64 to 8bit by delorie.com id pA1HVW4d028236

I've built from source (gfortran) an application that won't run (cannot
execute binary file) and the "file" command prompts: PE32 executable
(console) Intel 80386, for MS Windows. (Yes, chmod 755 is set for the
executable...)

Funny thing is that I did the same build on a different machine with
sucess. Obviously there are differences between those machines, but I
can't think of what makes the difference here. Well, there is one major
difference: the Cygwin istallation on the sucessfull one is owned an run
as admin. On the other machine the Cygwin installation is non-admin, and
I even renamed the setup file to avoid the question of installation
permissions. 

Could the non-successful build be affected by the non-admin
installation?

Are there any debug options here?

Cheers,
KÃ¥re

- Raw text -