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=Gp6GsDmmlAmVuohpGXbLF4j04Z/I/mNQf0WpbpZ5mzOGY+qIZpp/P
	qID/c9azorRjeQnbC1idaClYbc2ernmUomEvqZaktU0ApX/gCv/YHV8l24r/GD9N
	YiOXSBKdKkiA11gsi05c80GBlR2IvkgzH9eAEqKrcOWxVakkFpSzFw=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Fri, 4 Apr 2014 13:37:38 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Trouble with running cygwin dll on Vortex86MX+ CPU
Message-ID: <20140404113738.GF2508@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <loom.20140403T003453-906@post.gmane.org> <20140404083359.GD2508@calimero.vinschen.de> <loom.20140404T113717-470@post.gmane.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="s0H35NU0PUc8VBh+"
Content-Disposition: inline
In-Reply-To: <loom.20140404T113717-470@post.gmane.org>
User-Agent: Mutt/1.5.21 (2010-09-15)

--s0H35NU0PUc8VBh+
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Apr  4 09:44, Colin wrote:
> Corinna Vinschen <corinna-cygwin <at> cygwin.com> writes:
>=20
> > > In discussing this with the embedded PC supplier, he suggests that th=
e=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, o=
r=20
> > > must I give up on using cygwin for this application?
> >=20
> > 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.
> >=20
> > I'm not trying to discourage you, but you might have a lot of
> > experimenting to do to get this working.
> >=20
> > Corinna
> >=20
> Thanks Corinna for this information. Now I understand the underlying issu=
e=20
> and can decide how to move forward.=20
>=20
> Given that my application is not so big, I suspect that the pragmatic=20
> course will be to re-code it for Win32.=20

Alternatively, even though I hate to point people to older versions
of Cygwin, you could try the old Cygwin 1.5.25.  I'm not quite sure,
but I think it was compiled for i586 or even i386.  It's not as
feature-rich as Cygwin 1.7 but it worked, and maybe the set of
POSIX functions is sufficient for you.  See the Cygwin time machine
at http://www.fruitbat.org/Cygwin/index.html#cygwincirca

If you want to go even further back in time, then MSYS may be the
right thing for you.  It's a rip-off of Cygwin 1.3.22 with a few
patches to supposedly building native executables a bit better.
Just make sure to grab the old MSYS, not the more recent MSYS2.
See http://www.mingw.org/wiki/MSYS


HTH,
Corinna

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

--s0H35NU0PUc8VBh+
Content-Type: application/pgp-signature

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

iQIcBAEBAgAGBQJTPpmCAAoJEPU2Bp2uRE+gxOQQAJAFS9cMrMGha1PixceC/w3Z
mf48UTJ4OuL44+hk0nso6a5wAIh3RcJL+F58v/Ihore/LksuODNczfCYSet0UWF1
fD6EerHaWO+NQkPxvaCKI1fChM+2IQZOEQlFh4wiY2lbN5Uh9QTXgV2dOOiQh2f3
5xQ7zOTzeLfEJia84MUoY96QCWKomlXMZaoeY/eB2boQ1NHyQ3IRixumw043XuZ6
GATYc6t3oI04G0m/QRESNFQjlait0s6EXuJ4lbPf+L0R/IGW19PTzEHesw8XhWzb
6UoKtPCi938xwhHAxnnQ/WhDeqRkJlNvEsbdg7lpvJ9Db5qJQ6bZL8mUf4DI0eNd
kZkXs+V8LJvK61iCuxLqczOMz6Yu7iPyl7sOLgZUGUwqiOV2IyZ5slh34P+uRKVi
ixJEam8aWofTSdcFduZ9WJ1//iZgPXtyoW71QMX3sFAdIWWF2TRFnqSz68NhhApw
CuIM6Duug8ICB0UaJT620fzZbsrz3QtKMksCgf7hJ+qBYCCzK2bMABJKueHNJA7f
TyS6KRRBGHuz8VduIwgkjrRO8UW5HwpQzFI6bzA0h7AND5hDoN2kBFOTdscwv3jH
/W8fy2PjetRQNGW3vrYRQAKaVMv2UKRrQ9QR/8aAF/5mmoHW1oWavX/0AkIw9r08
noyzAWBu2A3971BqJnyz
=VxSp
-----END PGP SIGNATURE-----

--s0H35NU0PUc8VBh+--