From: "Ronald Fischer" <ynnor@mm.st>
To: "Ken Brown" <kbrown@cornell.edu>,
"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: BUG: exec format error: emacs
Date: Mon, 20 Jan 2020 07:19:00 -0000 [thread overview]
Message-ID: <9b676e51-62fa-490d-a84f-177a7976ea49@www.fastmail.com> (raw)
In-Reply-To: <2bf77d8d-0f31-e566-c63d-99c6b1484142@cornell.edu>
On Fri, Jan 17, 2020, at 17:16, Ken Brown wrote:
> On 1/17/2020 10:33 AM, Ronald Fischer wrote:
> > When trying to run `emacs`, I get
> >
> > (on zsh) : zsh: exec format error: emacs
> > (on bash): bash: /usr/bin/emacs: cannot execute binary file: Exec format error
>
> Are you sure Cygwin's emacs is the first one in your path?
Well, at least you can see from the error message that /usr/bin/emacs is going to be executed.
> Cygwin's
> /usr/bin/emacs should be a symlink:
Actually, this is not the case:
$ ls -l /usr/bin/emacs
-rwxrwx---+ 1 FISRONA Domain Users 60 Apr 26 2019 /usr/bin/emacs
$ stat /usr/bin/emacs
File: /usr/bin/emacs
Size: 60 Blocks: 1 IO Block: 65536 regular file
Device: 38d54b25h/953502501d Inode: 1407374883785092 Links: 1
Access: (0770/-rwxrwx---) Uid: (3672028/ FISRONA) Gid: (1049089/Domain Users)
Access: 2019-06-03 12:34:56.255711900 +0200
Modify: 2019-04-26 20:48:58.000000000 +0200
Change: 2019-06-03 12:34:56.255711900 +0200
Birth: 2019-06-03 12:34:56.255711900 +0200
Two things I find of interest here: Although I have installed the new version using Cygwin's set-up program just a couple of days ago, the modify time goes back to 2019.
And the size is too small!
Ronald
--
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
next prev parent reply other threads:[~2020-01-20 7:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 15:33 Ronald Fischer
2020-01-17 16:16 ` Ken Brown
2020-01-20 7:19 ` Ronald Fischer [this message]
2020-01-20 8:08 ` Ronald Fischer
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=9b676e51-62fa-490d-a84f-177a7976ea49@www.fastmail.com \
--to=ynnor@mm.st \
--cc=cygwin@cygwin.com \
--cc=kbrown@cornell.edu \
/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).