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:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=taNIgVv8eGT9iISH
	Ohayx2xOXoxDqZQX5WHK1SKvA7f1lXds/9x/NCoDmuVSC8RdG0u/adgbQFfghZ/g
	0yaXsq9vQ9Vp1QtzaWI/W3cTGsbsI/AgjQo8hUNmGMU3o/RlnZ9aJlNHvoKo5yId
	b4jnKO0Cm6XUFVsJhBeVvOERYr0=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Mon, 9 Jul 2018 05:18:34 +0300
From: Andrey Repin <anrdaemon@yandex.ru>
Reply-To: cygwin@cygwin.com
Message-ID: <1124060518.20180709051834@yandex.ru>
To: Ulli Horlacher <framstag@rus.uni-stuttgart.de>, cygwin@cygwin.com
Subject: Re: running self compiled 32 bit binary on 64 bit Windows?
In-Reply-To: <20180709002131.GA3525@rus.uni-stuttgart.de>
References: <20180606115005.GA15015@rus.uni-stuttgart.de>   <0F7D3B1B3C4B894D824F5B822E3E5A17787FB4BB@IRSMSX102.ger.corp.intel.com>  <3110356010.20180606204945@yandex.ru>  <540c62ab-2519-9f57-6565-d536d8b74ef2@gmail.com>  <944481618.20180607010455@yandex.ru>  <20180608133017.GB20898@rus.uni-stuttgart.de>  <0F7D3B1B3C4B894D824F5B822E3E5A17787FD684@IRSMSX102.ger.corp.intel.com>  <20180608135221.GF20898@rus.uni-stuttgart.de>  <49498971.20180608194124@yandex.ru> <20180709002131.GA3525@rus.uni-stuttgart.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Greetings, Ulli Horlacher!

> On Fri 2018-06-08 (19:41), Andrey Repin wrote:

>> >> 2.) Do a Cygwin build and copy cygwin1.dll
>> 
>> > I already have a /usr/bin/cygwin1.dll on the Windows 8 target system.
>> 
>> It's a wrong architecture. You need a 32-bit one for your 32-bit program.
>> 
>> > Do I have to replace it?
>> 
>> No.
>> Just build a 64-bit version of your program.

> SIGH. I was hoping a 32 bit cygwin with 32 bit self compiled programs will
> run on 64 bit Windows, too. But I was wrong.
> Meanwhile I have 4 VMs:
> Windows 32 bit with 32 bit cygwin
> Windows 32 bit with 32 bit cygwin for compiling
> Windows 64 bit with 64 bit cygwin
> Windows 64 bit with 64 bit cygwin for compiling

You can install both 32 and 64-bit Cygwin on the same machine.
So you don't really need 4, while I see how having a build system separate is
a good idea.

>> > This is what I first did:
>> > Transfered the 32 bit cygwin with my self compiled binaries
>> 
>> You have to install Cygwin, not "transfer".

> I have several 100 users, none of them is able to install cygwin

*You* have to do it.
Cygwin offers tools to automate process.

> and the packages they need the official way, they are way to *CENSORED* for
> this job :-} 
> I give them my preconfigured cygwin.zip (or cygwin64.zip) and tell them to
> unpack it in C:\

> http://fex.belwue.de/usecases/cygwin.html

> (This is what I call "transfer cygwin")

> This works so far without problems.

Only by accident and promise.


-- 
With best regards,
Andrey Repin
Monday, July 9, 2018 5:16:37

Sorry for my terrible english...


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