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:references
	:mime-version:content-type:content-transfer-encoding; q=dns; s=
	default; b=X/lixD5EM7P1Iocz02WiZRBP5eYC+ZZJiK3yDAXeEv1CddGr6Jxbx
	wpgORivZRuuwJxXCIHJphHXO38+VIbHrg7rLEy4S8xiiC3FJeea/i8NRz/UbRbP2
	5NJYW/eOgOXrUspapcrfm6XxL4N/j+iQcLxC4Ewsmulm+p90AIqb3g=
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:references
	:mime-version:content-type:content-transfer-encoding; s=default;
	 bh=c8nCaGrDrl5ySSdZDfK8CpY2vmQ=; b=Ra/qI5wEgHFE8yFPJUuUmEK7Q0sE
	LCcML4ZM/qLZszEeVNuEXROc4ehkevNCykkIZvuDCa9cS2WdUV4HZeirF5ZhsF5h
	lYvAiwkaqsbaPSaSN1reH16W5Dm8M2Wvki0bR2Q1EGDDJNEHaEH6ZTMT4TXTZzwC
	Galq/a+ah+59O/U=
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=-2.5 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS,UNPARSEABLE_RELAY autolearn=ham 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: Re: Trouble with running cygwin dll on Vortex86MX+ CPU
Date: Fri, 4 Apr 2014 09:44:19 +0000 (UTC)
Lines: 30
Message-ID: <loom.20140404T113717-470@post.gmane.org>
References: <loom DOT 20140403T003453-906 AT post DOT gmane DOT org> <20140404083359 DOT GD2508 AT calimero DOT vinschen DOT de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
User-Agent: Loom/3.14 (http://gmane.org/)
X-IsSubscribed: yes

Corinna Vinschen <corinna-cygwin <at> cygwin.com> writes:

> > 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?
> 
> 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
> 
Thanks Corinna for this information. Now I understand the underlying issue 
and can decide how to move forward. 

Given that my application is not so big, I suspect that the pragmatic 
course will be to re-code it for Win32. 

Cheers, 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