From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 112761 invoked by alias); 8 Jun 2018 13:52:27 -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 112747 invoked by uid 89); 8 Jun 2018 13:52:26 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 spammy=mot, Tel, tel X-HELO: smtp02.belwue.de Received: from smtp02.belwue.de (HELO smtp02.belwue.de) (129.143.71.87) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 08 Jun 2018 13:52:24 +0000 Received: from fex.rus.uni-stuttgart.de (fex.rus.uni-stuttgart.de [129.69.1.129]) by smtp02.belwue.de (Postfix) with SMTP id F36CD5AF7 for ; Fri, 8 Jun 2018 15:52:21 +0200 (MEST) Date: Fri, 08 Jun 2018 13:52:00 -0000 From: Ulli Horlacher To: "cygwin@cygwin.com" Subject: Re: running self compiled 32 bit binary on 64 bit Windows? Message-ID: <20180608135221.GF20898@rus.uni-stuttgart.de> Mail-Followup-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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0F7D3B1B3C4B894D824F5B822E3E5A17787FD684@IRSMSX102.ger.corp.intel.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-IsSubscribed: yes X-SW-Source: 2018-06/txt/msg00097.txt.bz2 On Fri 2018-06-08 (13:43), Soegtrop, Michael wrote: > are you sure you want a cygwin build? I thought you are doing a MinGW > build (since Cygwin1.ddl was missing from ldd). What is MinGW? > 1.) Do a MinGW cross compile in case you don't need any Cygwin > infrastructure (bash, ...) or fully posix compliant C environment I need bash and posix environment! > 2.) Do a Cygwin build and copy cygwin1.dll I already have a /usr/bin/cygwin1.dll on the Windows 8 target system. Do I have to replace it? > 3.) Do a Cygwin build and install a matching cygwin on the destination > machine in case you need not just a posix compliant C environment, but > also a bash or other Unix tools This is what I first did: Transfered the 32 bit cygwin with my self compiled binaries to the 64 bit Windows 8. But then I was not able to use perl, I got a MOT of these errors: 0 [main] perl 4232 child_info_fork::abort: address space needed by 'Encode.dll' (0x370000) is already occupied Can't fork, trying again in 5 seconds at /client/bin/fexsend line 106. 1 [main] perl 7720 child_info_fork::abort: address space needed by 'Encode.dll' (0x370000) is already occupied Can't fork, trying again in 5 seconds at /client/bin/fexsend line 106. 1 [main] perl 5484 child_info_fork::abort: address space needed by 'Encode.dll' (0x370000) is already occupied Can't fork, trying again in 5 seconds at /client/bin/fexsend line 106. See my mail: From: Ulli Horlacher To: cygwin@cygwin.com Subject: Perl child_info_fork runtime error Date: Wed, 30 May 2018 12:57:09 +0200 These error are gone after I replaced the 32 bit cygwin with a 64 bit cygwin installation. -- Ullrich Horlacher Server und Virtualisierung Rechenzentrum TIK Universitaet Stuttgart E-Mail: horlacher@tik.uni-stuttgart.de Allmandring 30a Tel: ++49-711-68565868 70569 Stuttgart (Germany) WWW: http://www.tik.uni-stuttgart.de/ REF:<0F7D3B1B3C4B894D824F5B822E3E5A17787FD684@IRSMSX102.ger.corp.intel.com> -- 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