delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2014/04/03/17:22:41

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
:in-reply-to; q=dns; s=default; b=gAuegA7Fz7SokN+JBkgu7LBzX4Q3vV
TB0eRcZALdyjACc5zGw7DzgAfjCXkXJ8hm3lnqLyTCvmA9L4e7w0oC3X405M1F9m
NvF6Os15ZMgYt34R/AugH3eK6ImNrX6icZ3elXxYTqyUzHXhrLSaZPxWzTnBbfyA
G4mYsIjemWByw=
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
:in-reply-to; s=default; bh=9lXNCWsNtbzoLnLeMh0z0kZfcak=; b=qVu8
gvn/nrkFbdfqpyjUPGW8HprfaL2UtVU9LN4BGFUMZ2vb9/RZfiI/ey5doHJIcUqg
5huDP6LGs4TCxiI0mpJuv/a1cM63LcjpTxRCggLj2HeS9J1/qwGQAwtzyMP0ZQbj
yYaVXjlTiL4lXDq4zYhPnB7QS0UfrklQLiTeDQ0=
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=0.7 required=5.0 tests=BAYES_00,FSL_HELO_BARE_IP_2,RCVD_IN_DNSWL_NONE,RCVD_NUMERIC_HELO,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: =?ISO-8859-1?Q?Ren=E9_Berber?= <r DOT berber AT computer DOT org>
Subject: Re: Trouble with running cygwin dll on Vortex86MX+ CPU
Date: Thu, 03 Apr 2014 15:21:07 -0600
Lines: 48
Message-ID: <lhkjdv$ph3$1@ger.gmane.org>
References: <loom DOT 20140403T003453-906 AT post DOT gmane DOT org>
Mime-Version: 1.0
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.19) Gecko/20081209 Lightning/0.9 Thunderbird/2.0.0.19 Mnenhy/0.7.6.0
In-Reply-To: <loom.20140403T003453-906@post.gmane.org>
X-IsSubscribed: yes

On 4/2/2014 5:03 PM, Colin wrote:
 > Hi Team,

Team?   This is a user's forum.

[snip]
 > 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...

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

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

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.

 > And if it is, is there a solution available, or
 > must I give up on using cygwin for this application?

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.
-- 
René Berber


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


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019