X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:mime-version
	:content-type:content-transfer-encoding; q=dns; s=default; b=DmW
	pfi2Hr+YcANFg29RYmcZ+1YPJmjnGcnhKHzyWr4RkBU/j+s+oXfCC0XCJqRuA301
	slaadK6HT+mMna6FrJ6j0keLKJvJqcGySALvzLU7zxI+Jusuyn36G166XODyhP5K
	JbyX4uv6vbG5WmcQCxe/h9F4zNSLxvCe5IGvs9HA=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:mime-version
	:content-type:content-transfer-encoding; s=default; bh=LcfkWRPQe
	dzwJgbr5FQkU1bWvKw=; b=bPdRWsZwSxndSNmGXQiPfJdt7ciNaS+Bmrhe6+P7Y
	neY5xirQ3c+ip7eLnlzrJ+z/VbjWvGPnXT1ftgUuH2Tt2dOWfmxJSt1JOtoO1Ipa
	dmFDb3TY9sQW4fUuwCWnzturrSvoTTcw0FR7vb+ySWsfRNdpaaao9y2hX3IMPHC5
	8Y=
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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-1.4 required=5.0 tests=BAYES_00,DATE_IN_PAST_12_24,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=no version=3.3.2
X-HELO:	plane.gmane.org
To:	cygwin AT cygwin DOT com
From:	Colin <colin DOT wall AT gallagher DOT co>
Subject:	Trouble with running cygwin dll on Vortex86MX+ CPU
Date:	Wed, 2 Apr 2014 23:03:29 +0000 (UTC)
Lines:	28
Message-ID:	<loom.20140403T003453-906@post.gmane.org>
Mime-Version:	1.0
User-Agent:	Loom/3.14 (http://gmane.org/)
X-IsSubscribed:	yes

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

- Raw text -