From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1233 invoked by alias); 8 Jun 2018 17:44:10 -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 1219 invoked by uid 89); 8 Jun 2018 17:44:09 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No 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=canada, Canada, lacked X-HELO: smtp-out-no.shaw.ca Received: from smtp-out-no.shaw.ca (HELO smtp-out-no.shaw.ca) (64.59.134.12) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 08 Jun 2018 17:44:07 +0000 Received: from [192.168.1.100] ([24.64.240.204]) by shaw.ca with ESMTP id RLQhf93m8uYopRLQifc9se; Fri, 08 Jun 2018 11:44:04 -0600 X-Authority-Analysis: v=2.3 cv=GopsBH9C c=1 sm=1 tr=0 a=MVEHjbUiAHxQW0jfcDq5EA==:117 a=MVEHjbUiAHxQW0jfcDq5EA==:17 a=IkcTkHD0fZMA:10 a=_gqmDMfD322UtP85MhQA:9 a=QEXdDO2ut3YA:10 a=WspVwsfix1wA:10 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> <20180608134248.GC20898@rus.uni-stuttgart.de> From: Brian Inglis Openpgp: preference=signencrypt Message-ID: <8c094a4b-1fe9-2993-f1c5-01aa0852c7df@SystematicSw.ab.ca> Date: Fri, 08 Jun 2018 17:44:00 -0000 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: <20180608134248.GC20898@rus.uni-stuttgart.de> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfOnDbkNMEhjv//jaMflglP+HKdt/152fN9B3DVB7lGTjREsAGKgjYjivK11ZiHq/I+22JQI0x0/vCEAQZw+FSoqCscxlXgUXP7+qR6bDQYEWH+oW/iVB 0fY2ABvXUkANWznPBq5bDtKEUwO37ZOJubswL/KaeOPSKNQ7UView+a2k9+yqCEEbjzn0+rPIbe+xw== X-IsSubscribed: yes X-SW-Source: 2018-06/txt/msg00107.txt.bz2 On 2018-06-08 07:42, Ulli Horlacher wrote: > On Wed 2018-06-06 (16:12), cyg Simple 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. > jed comes with a BIG makefile. > When I start it, it outputs: > /sw/src/jed-0.99.20-116: make > cd src; make jed > make[1]: Entering directory '/sw/src/jed-0.99.20-116/src' > gcc -O -I/sw/cygwin-7_32/slang-2.3.1-88/include -L/sw/cygwin-7_32/slang-2.3.1-88/lib -DSLANG_DLL=1 -Dunix -DJED -I/sw/cygwin-7_32/slang-2.3.1-88/include /sw/src/jed-0.99.20-116/src/chkslang.c -o /sw/src/jed-0.99.20-116/src/objs/chkslang -L/sw/cygwin-7_32/slang-2.3.1-88/lib -lslang -lutil -lm -ldl > if /sw/src/jed-0.99.20-116/src/objs/chkslang jed 20203 ;\ > then exit 0; else rm -f /sw/src/jed-0.99.20-116/src/objs/chkslang; exit 1; fi > cd /sw/src/jed-0.99.20-116/src/objs; gcc -c -O -I/sw/cygwin-7_32/slang-2.3.1-88/include -L/sw/cygwin-7_32/slang-2.3.1-88/lib -DSLANG_DLL=1 -Dunix -DJED -I/sw/cygwin-7_32/slang-2.3.1-88/include /sw/src/jed-0.99.20-116/src/buffer.c >>> 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)? > Cygwin bash >> What happens if you use cmd.exe? > Currently I cannot run cmd.exe, it crashes. > Maybe there is the problem? >>> admin@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@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@WIN-7T5P92ALEEB:/sw/cygwin-7_32/jed-0.99-20_116/bin: file jed >>> jed: PE32 executable (console) Intel 80386, for MS Windows >>> admin@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. > No, I have used cygwin gcc, I have no other compilers! >> Try: >> cmd /c start cmd > A windows pops up and immediatelly closes. Use whatever Windows shortcuts are provided to launch cmd; try as user and as admin to see if there are differences; or from a Cygwin shell run: $ cygstart `cygpath $COMSPEC` /k as /k keeps the window around so you can see any (error) messages. To run Cygwin 32 under Windows 64, you have to download and run setup-x86 to set up the Cygwin 32 registry entries and base environment. If you add .../cygwin32/bin to your user PATH (after .../cygwin64/bin if you have that installed) you can then run Cygwin 32 exes from Cygwin 64 or Windows 64 shells. As stated, this is not recommended, but a number of us probably ran that way for years, as Cygwin 64 initially lacked a lot of packages available only on Cygwin 32. For a few years now, packages to be released must be built and made available for both Cygwin 32 and 64 environments. -- 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