From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15815 invoked by alias); 9 Jul 2018 06:22:21 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 15801 invoked by uid 89); 9 Jul 2018 06:22:20 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=fex.belwue.de, UD:belwue.de, UD:cygwin.html, cygwinhtml X-HELO: smtp-out-so.shaw.ca Received: from smtp-out-so.shaw.ca (HELO smtp-out-so.shaw.ca) (64.59.136.139) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 09 Jul 2018 06:22:18 +0000 Received: from [192.168.1.100] ([24.64.240.204]) by shaw.ca with ESMTP id cPYtfvDaubP3IcPYufdAgl; Mon, 09 Jul 2018 00:22:16 -0600 Reply-To: Brian.Inglis@SystematicSw.ab.ca Subject: Re: running self compiled 32 bit binary on 64 bit Windows? To: cygwin@cygwin.com 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> <1124060518.20180709051834@yandex.ru> From: Brian Inglis Openpgp: preference=signencrypt Message-ID: <47172619-d88a-6e62-bb01-df3de0ea9f4a@SystematicSw.ab.ca> Date: Mon, 09 Jul 2018 06:22:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.0 MIME-Version: 1.0 In-Reply-To: <1124060518.20180709051834@yandex.ru> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2018-07/txt/msg00073.txt.bz2 On 2018-07-08 20:18, Andrey Repin wrote: >> 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. He just means that you must provide matching Cygwin DLLs and exes which are either all built as x86 (32 bit), or all as x86_64. Cygwin x86 programs will run on Windows x64 or x86 desktops as they support x86 programs. >From Windows Server 2008 R2, all *servers* are x64 only, and x86 support is an optional installable feature on *servers*, except it is still required for AD support, which MS has still not rewritten for x64. >> 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. More explanation would be helpful. He could setup a package download structure, including setup-x86[_64].exe and setup.ini, zip that for transfer, unzip that in a known location, then run the included setup in unattended mode with fixed arguments, to setup the Cygwin environment, install the base and other packages. Have you other suggestions? >> 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. More explanation would be helpful. What problems do you see with his process? -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada -- 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