DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:reply-to:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=c5TFDTD0Ktv311jm
	wvyTGEq246VvzlGzivzQQC17U8UpPli7z1ITpWo+6TKQfVShG/5yi+IbsoBf9V6k
	xx1Fj89SpQow678q/sNe1up3Q/x6g2YFLB3kbKVLvdKS4gc1/FAhvG9wKiopnFLK
	UbGxIXjqCv+AgGZnxdfQnxpxyjQ=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Subject: Re: running self compiled 32 bit binary on 64 bit Windows?
To: cygwin AT cygwin DOT com
References: <20180606115005 DOT GA15015 AT rus DOT uni-stuttgart DOT de>
Reply-To: cygwin AT cygwin DOT com
From: cyg Simple <cygsimple AT gmail DOT com>
Openpgp: preference=signencrypt
Message-ID: <ec20b090-01b8-c6fd-71a3-32165e11bed4@gmail.com>
Date: Wed, 6 Jun 2018 16:12:51 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <20180606115005.GA15015@rus.uni-stuttgart.de>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

On 6/6/2018 7:50 AM, Ulli Horlacher wrote:
> 
> On Windows 7 32 bit I have compiled some binaries by myself.

Help us help you by giving us how you compiled these and with what set
of tools.

> I can run them there but not on a Windows 8 64 bit: no (error) message,
> nothing happens.
> 

In what shell are you running these (Cygwin bash, cmd.exe, etc)?
What happens if you use cmd.exe?

> admin AT WIN-7T5P92ALEEB:/sw/cygwin-7_32/jed-0.99-20_116/bin: uname -a
> CYGWIN_NT-6.3 WIN-7T5P92ALEEB 2.10.0(0.325/5/3) 2018-02-02 15:16 x86_64 Cygwin
> 
> admin AT WIN-7T5P92ALEEB:/sw/cygwin-7_32/jed-0.99-20_116/bin: ll jed
> -rwxr-xr-x  admin    None     480,235 2018-04-10 11:58:59 jed
> 
> admin AT WIN-7T5P92ALEEB:/sw/cygwin-7_32/jed-0.99-20_116/bin: file jed
> jed: PE32 executable (console) Intel 80386, for MS Windows
> 
> admin AT WIN-7T5P92ALEEB:/sw/cygwin-7_32/jed-0.99-20_116/bin: ldd jed
>         ntdll.dll => /cygdrive/c/Windows/SYSTEM32/ntdll.dll (0x7ffe0e520000)
>         ??? => ??? (0x77330000)
>         wow64.dll => /cygdrive/c/Windows/SYSTEM32/wow64.dll (0x772d0000)
>         wow64win.dll => /cygdrive/c/Windows/system32/wow64win.dll (0x77260000)
>         wow64cpu.dll => /cygdrive/c/Windows/system32/wow64cpu.dll (0x77320000)
>         

No mention of Cygwin in this list so you must have used a non-cygwin
tool to build the package.

> admin AT WIN-7T5P92ALEEB:/sw/cygwin-7_32/jed-0.99-20_116/bin: ./jed

Try:
cmd /c start cmd

In the new command window:
jed

> admin AT WIN-7T5P92ALEEB:/sw/cygwin-7_32/jed-0.99-20_116/bin: 
> 
> 
> Do I have to install some 32 bit libs? Which ones?
> 

We don't know yet, you might try using GDB to capture the error but
until we have more we can't help further.

-- 
cyg Simple

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