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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=qKVKBkh4VuDZPXZLvO4upCa5nVnxSLBL1RohUfjDRB0l9baHWl4ex
	bwYbaXJ+y2s4jttq5p+Tkwn2OXqS0XNQyetHmXp9qPuuRGgcPfN1kcyc6LCW3l8I
	Vrnb3n4NBTcXT6c0u58cETRG346lA0qf3BHhwlcRPkqJmZan6TOlbk=
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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=ZWrxnum6J9TzJYfGIctNZHsuqFA=; b=a+tDLA4czucWeM753Z8H+ywDnsO9
	jda0DjItfKNfWFfKYTRz5tZ6S/PqzkufW6uw6TzSO9fryA6tcHOBVSTHH3SbpfiM
	cRNJjbMaUU7b1T3be9zBx2ujJ9hYWcolQhoaIKQqJv0kAwD17HJI0vh8SVrZ3ktk
	XG44YmB+uYBISvY=
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=-5.9 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2
X-HELO:	calimero.vinschen.de
Date:	Fri, 4 Apr 2014 10:33:59 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Trouble with running cygwin dll on Vortex86MX+ CPU
Message-ID:	<20140404083359.GD2508@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<loom DOT 20140403T003453-906 AT post DOT gmane DOT org>
MIME-Version:	1.0
In-Reply-To:	<loom.20140403T003453-906@post.gmane.org>
User-Agent:	Mutt/1.5.21 (2010-09-15)

--QCC2I/2CckNfI+Tr
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Apr  2 23:03, Colin wrote:
> Hi Team,
>=20
> I'm new here, but have dabbled in Cygwin for a few years. I hope someone=
=20
> more knowledgeable than myself can help with with this issue which is=20
> quite frankly baffling me for the past few weeks.
>=20
> The problem I have can be reduced to this: I compile a simple "Hello=20
> World" console mode c program. I copy the .exe file and cygwin1.dll onto=
=20
> an embedded PC, open a console window, and run the program. The program=
=20
> runs, and returns immediately to the command prompt, with no output. No=
=20
> error messages, no nothing...
>=20
> I can do the same on any desktop PC running Windows XP, or 7, my "Hello=
=20
> World" runs as expected.
>=20
> The embedded PC is currently running a full installation of Windows XP=20
> Professional, SP3. It does so quite happily. It's CPU is DM&P Vortex86MX+=
=20
> 933MHz. I am able to run a "Hello World" program compiled with a native=
=20
> Windows compiler on it successfully.

I had a quick look into the programmer's manual for this CPU, and per
this document the CPU is i486DX compatible.  This could be the problem.
The Cygwin GCC defaults to i686 for a long time and naturally the Cygwin
DLL as well as your own application are built for i686.

> In discussing this with the embedded PC supplier, he suggests that the=20
> cygwin1.dll is exiting because it doesn't recognise the CPU. Is this=20
> explanation plausible? And if it is, is there a solution available, or=20
> must I give up on using cygwin for this application?

As far as the pre-built Cygwin goes, I fear that you can't do a lot.
You could try to build Cygwin in i486 mode, and if that works, you have
to make sure to build applications against the newly built crt0.o and
libcygwin.a.  But that's not all to keep in mind.  When building
applications, parts of GCC are linked in as well, namely crtbegin.o and
crtend.o, and sometimes cyggcc_s-1.dll.  All these may or may not use
post-i486 opcodes, so if push comes to shove you'd end up having to
rebuild GCC for i486 as well.

I'm not trying to discourage you, but you might have a lot of
experimenting to do to get this working.


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--QCC2I/2CckNfI+Tr
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJTPm53AAoJEPU2Bp2uRE+g7PMP/RTaH6oOL9AA0nhkw8LD6hq0
EHhFq6AG1tqMwuIH9iv5Laum4nKoHizbmlkC5jL6fOhUWJYObWFEyHYoA1sZHU5C
VmGvMV82twEKo6JuoGXnoub2XnJZP5wnxHmAaudLs0B4vmMHAZ3l9/i6ifHLEmH3
z3L5ORfHHsjFHmfZbZOZcKeGqp2vE8OaAEiyBU53RwEtCgCgl5l7OjomqAYbNOaj
I0sbPI6MOFEJaKz0GpQEECbhiP7NR5xZam900tn3UyzJ7PgDSNqtY7P3X++svmJT
RR4gXhhe2uYLhV4YyXBAGjD4vNyZmnNsQwVAcj6WOCXoLIEN9oqaELyo/Y1m0aRX
MThhj4OsVwBzmtbOWajxcsZGBph7VCcgGSjicyi9STD+XzQv/dw3mjw3XEjBXrWz
j4Mi48x/mROGJm0sESiGT5sCP6rnxmx9JTdldeXMrFYO6BVwP0mUs9q2gf9Rd364
O+OV8i9nOkn7sS9kz5J7CPAviBZewcc7D4cx4YI78Zzw5V5vEk5+bpf2PJdwdmXb
LVAbrSKLjJjP6pmkMqJ3DKLFQIZrsXCbdd4z1hitbDjeC/CjTWwDLY2qXamHbrg+
3dQWIG7EtRoj05PakftmBm4YoQrMMPcXui8WnlK0AQpdsoggY8Z/oadv5pKfVdfz
UcjYluCATSPYn4XNIsto
=Bley
-----END PGP SIGNATURE-----

--QCC2I/2CckNfI+Tr--

- Raw text -