From: "Edvardsen Kåre" <kare.edvardsen@uit.no>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: cannot execute binary file
Date: Tue, 01 Nov 2011 10:24:00 -0000 [thread overview]
Message-ID: <1320143047.5480.78.camel@kare-desktop> (raw)
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
next reply other threads:[~2011-11-01 10:24 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 10:24 Edvardsen Kåre [this message]
[not found] ` <4EAFE5F0.7090404@cs.umass.edu>
2011-11-01 13:00 ` Edvardsen Kåre
2011-11-02 8:11 ` Edvardsen Kåre
2011-11-02 8:42 ` Marco Atzeri
2011-11-02 11:01 ` Eliot Moss
2011-11-01 14:32 ` Edvardsen Kåre
-- strict thread matches above, loose matches on Subject: below --
2013-12-16 22:55 Gerry Reno
2013-12-17 0:27 ` Max Polk
2013-12-17 0:32 ` Gerry Reno
2013-12-17 2:39 ` Larry Hall (Cygwin)
2013-12-17 2:58 ` Gerry Reno
2013-12-17 9:35 ` Andrey Repin
2013-12-17 12:44 ` Tim Prince
2013-12-17 16:27 ` Gerry Reno
2013-12-17 18:59 ` Gerry Reno
2012-09-21 4:23 RobF
2012-09-21 7:54 ` P.Long
2012-09-21 8:27 ` Csaba Raduly
2012-09-21 13:06 ` RobF
2011-11-02 10:04 Edvardsen Kåre
2006-09-07 18:08 Cannot " Arun Biyani
2006-09-07 18:19 ` Dave Korn
2006-09-07 18:27 ` Christopher Faylor
2006-09-07 18:50 ` Arun Biyani
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1320143047.5480.78.camel@kare-desktop \
--to=kare.edvardsen@uit.no \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).