From: Colin <colin.wall@gallagher.co>
To: cygwin@cygwin.com
Subject: Trouble with running cygwin dll on Vortex86MX+ CPU
Date: Thu, 03 Apr 2014 19:20:00 -0000 [thread overview]
Message-ID: <loom.20140403T003453-906@post.gmane.org> (raw)
Hi Team,
I'm new here, but have dabbled in Cygwin for a few years. I hope someone
more knowledgeable than myself can help with with this issue which is
quite frankly baffling me for the past few weeks.
The problem I have can be reduced to this: I compile a simple "Hello
World" console mode c program. I copy the .exe file and cygwin1.dll onto
an embedded PC, open a console window, and run the program. The program
runs, and returns immediately to the command prompt, with no output. No
error messages, no nothing...
I can do the same on any desktop PC running Windows XP, or 7, my "Hello
World" runs as expected.
The embedded PC is currently running a full installation of Windows XP
Professional, SP3. It does so quite happily. It's CPU is DM&P Vortex86MX+
933MHz. I am able to run a "Hello World" program compiled with a native
Windows compiler on it successfully.
In discussing this with the embedded PC supplier, he suggests that the
cygwin1.dll is exiting because it doesn't recognise the CPU. Is this
explanation plausible? And if it is, is there a solution available, or
must I give up on using cygwin for this application?
Thanks for yout time.
Colin
--
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 reply other threads:[~2014-04-03 19:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 19:20 Colin [this message]
2014-04-03 21:22 ` René Berber
2014-04-04 8:07 ` Colin
2014-04-04 8:34 ` Corinna Vinschen
2014-04-04 9:44 ` Colin
2014-04-04 11:37 ` Corinna Vinschen
2014-04-07 11:08 ` Colin
2014-04-07 11:23 ` Corinna Vinschen
2014-04-07 16:30 ` Larry Hall (Cygwin)
2014-04-07 21:10 ` Colin
2014-04-07 22:12 ` Larry Hall (Cygwin)
2014-04-07 22:49 ` Peter A. Castro
2014-04-08 1:28 ` Larry Hall (Cygwin)
2014-04-08 1:50 ` Christopher Faylor
2014-04-08 1:59 ` Larry Hall (Cygwin)
2014-04-15 21:52 ` Peter A. Castro
2014-04-16 13:21 ` Achim Gratz
2014-04-16 16:02 ` Peter A. Castro
2014-04-16 16:20 ` Achim Gratz
2014-04-08 2:14 ` Peter A. Castro
2014-04-07 23:26 ` Duncan Roe
2014-04-14 8:37 ` Colin
2014-04-04 8:40 ` Yaakov (Cygwin/X)
2014-04-04 9:57 ` Colin
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=loom.20140403T003453-906@post.gmane.org \
--to=colin.wall@gallagher.co \
--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).