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=I5u6DN0VBucA7Xequd7/WLgk2yQg7N4BYMyojgeOIKM71n3nbeARG
	SDFF3VjRpGLckkalRZRa1c4Rfb5fXz3Io6ADcUnrkA7r1TybY5d0py9MWtpZjV99
	ENQRXRLmQTsTf5bOMgMTaHeLJVZVB+3JqX/r1li+lbITxti2yGrcaA=
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=eZ0MtaD6U5EXhuB2k1omR53xA/0=; b=Tgvi/tYKelkqwHS/pd+nqEFQ2+4F
	h3uRpxvwyKCk4HdkPXHZ67WyRLgELhq+GX8rQZcJyODcuWauhx6nWkmJJ5dXrBf2
	GDm7ECIHj38TpGeeXyRi5GJS5z/KUIzGlYIoXtjm0yI6YSN+OvLeh0qkv731ELlY
	jzviqsG0NhU3Hls=
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 08:06:54 +0000 (UTC)
Lines:	46
Message-ID:	<loom.20140404T094005-949@post.gmane.org>
References:	<loom DOT 20140403T003453-906 AT post DOT gmane DOT org> <lhkjdv$ph3$1 AT ger DOT gmane DOT org>
Mime-Version:	1.0
User-Agent:	Loom/3.14 (http://gmane.org/)
X-IsSubscribed:	yes

René Berber <r.berber <at> computer.org> writes:
 
> 
> What you usually do on those cases:
> 
> 1. On the build host, run ldd (or cygcheck) on the program, see the full 
> list of dynamic libraries used.
> 
> 2. Try to do the same on the target host.  Yes, ldd does depend on 
> cygwin1.dll, so it may not run.  cygcheck doesn't depend on the 
> cygwin1.dll .
 
I'll do some more of this next week when back at work. I did do cygcheck -s 
-v -r on the target (from the Cygwin Reporting Problems page) but it 
produced no output.

>  > I can do the same on any desktop PC running Windows XP, or 7, my "Hello
>  > World" runs as expected.
> 
> For completeness sake, you mean a PC where Cygwin has not been installed?

That is correct

> 
>  > 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?
> 
> I don't know, but I doubt it.  As long as it is compatible with the 
> Intel x86 architecture, and Windows is a "complete" version, it should 
work.

That is what I had expected...

> 
> Cross-compilation from Cygwin to Win32 (MinGW, MinGW-w64) is still 
> possible, just needs a different set of tools which are available in the 
> Cygwin distributed packages.  Actually is a better option in your case, 
> unless you really want to use a long list of libraries which may not be 
> ported to Win32, or build programs intended for Unix/Linux.

My reason for using Cygwin was so as to re-use code originally written for 
Linux with POSIX serial ports etc.

Thank you for your help.



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