Re: running self compiled 32 bit binary on 64 bit Windows?
Greetings, Ulli Horlacher! > On Thu 2018-08-30 (15:55), Ulli Horlacher wrote: >> On Thu 2018-08-30 (11:43), Andrey Repin wrote: >> >> > > This script would run setup-x86_64.exe which asks a lot of questions >> > > (mirror site, proxy, installation directory, etc) in the first run. >> > > This will overcharge my users! >> > >> > setup --help >> >> There is no command line option for "Choose A Download Site" > ARGH, I have overlooked > -s --site Download site URL > > Sorry! It took less than 3 months... -- With best regards, Andrey Repin Friday, August 31, 2018 0:56:30 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
Re: running self compiled 32 bit binary on 64 bit Windows?
Ulli Horlacher writes: > This script would run setup-x86_64.exe which asks a lot of questions > (mirror site, proxy, installation directory, etc) in the first run. > This will overcharge my users! Well, after all the hints you've already got, how about you actually look at what setup.exe does when you give it some options to work with? ONce you've figured that out you can decide whether you'll want to provide your own repo for setup to install Cygwin and your software from or if you instruct setup to use two repos. Once it's working to your liking, package up the resulting command line in a batch script and tell your users to download both that script and setup.exe (or give them an archive with both or figure out a PowerShell incantation to do the downloads). Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds -- 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
Re: running self compiled 32 bit binary on 64 bit Windows?
On Thu 2018-08-30 (15:55), Ulli Horlacher wrote: > On Thu 2018-08-30 (11:43), Andrey Repin wrote: > > > > This script would run setup-x86_64.exe which asks a lot of questions > > > (mirror site, proxy, installation directory, etc) in the first run. > > > This will overcharge my users! > > > > setup --help > > There is no command line option for "Choose A Download Site" ARGH, I have overlooked -s --site Download site URL Sorry! -- Ullrich Horlacher Server und Virtualisierung Rechenzentrum TIK Universitaet Stuttgart E-Mail: horlac...@tik.uni-stuttgart.de Allmandring 30aTel:++49-711-68565868 70569 Stuttgart (Germany) WWW:http://www.tik.uni-stuttgart.de/ REF:<20180830135516.ga3...@rus.uni-stuttgart.de> -- 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
Re: running self compiled 32 bit binary on 64 bit Windows?
On Thu 2018-08-30 (11:43), Andrey Repin wrote: > > This script would run setup-x86_64.exe which asks a lot of questions > > (mirror site, proxy, installation directory, etc) in the first run. > > This will overcharge my users! > > setup --help There is no command line option for "Choose A Download Site" -- Ullrich Horlacher Server und Virtualisierung Rechenzentrum TIK Universitaet Stuttgart E-Mail: horlac...@tik.uni-stuttgart.de Allmandring 30aTel:++49-711-68565868 70569 Stuttgart (Germany) WWW:http://www.tik.uni-stuttgart.de/ REF:<923299097.20180830114...@yandex.ru> -- 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
Re: running self compiled 32 bit binary on 64 bit Windows?
Greetings, Ulli Horlacher! > On Sat 2018-07-14 (16:31), Achim Gratz wrote: >> > I have several 100 users, none of them is able to install cygwin and >> > the packages they need the official way, they are way to *CENSORED* for >> > this job :-} >> >> If they can follow your current instructions, they can surely start some >> script that does this correctly? > This script would run setup-x86_64.exe which asks a lot of questions > (mirror site, proxy, installation directory, etc) in the first run. You're still looking for excuses, instead of solutions. > This will overcharge my users! setup --help -- With best regards, Andrey Repin Thursday, August 30, 2018 11:43:05 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
Re: running self compiled 32 bit binary on 64 bit Windows?
Am 30.08.2018 um 08:40 schrieb Ulli Horlacher: On Sat 2018-07-14 (16:31), Achim Gratz wrote: I have several 100 users, none of them is able to install cygwin and the packages they need the official way, they are way to *CENSORED* for this job :-} If they can follow your current instructions, they can surely start some script that does this correctly? This script would run setup-x86_64.exe which asks a lot of questions (mirror site, proxy, installation directory, etc) in the first run. This will overcharge my users! You can put the defaults in the script. Something like setup-x86_64.exe -s http://www.mirrorservice.org/sites/sourceware.org/pub/cygwin/ -R d:\cygwin64 -n --local-package-dir d:\download\cygwin_cache -P see for details $ ./setup-x86_64.exe --help --- Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft. https://www.avast.com/antivirus -- 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
Re: running self compiled 32 bit binary on 64 bit Windows?
On Sat 2018-07-14 (16:31), Achim Gratz wrote: > > I have several 100 users, none of them is able to install cygwin and > > the packages they need the official way, they are way to *CENSORED* for > > this job :-} > > If they can follow your current instructions, they can surely start some > script that does this correctly? This script would run setup-x86_64.exe which asks a lot of questions (mirror site, proxy, installation directory, etc) in the first run. This will overcharge my users! -- Ullrich Horlacher Server und Virtualisierung Rechenzentrum TIK Universitaet Stuttgart E-Mail: horlac...@tik.uni-stuttgart.de Allmandring 30aTel:++49-711-68565868 70569 Stuttgart (Germany) WWW:http://www.tik.uni-stuttgart.de/ REF:<87d0vp7uth.fsf@Rainer.invalid> -- 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
Re: running self compiled 32 bit binary on 64 bit Windows?
Ulli Horlacher writes: >> You have to install Cygwin, not "transfer". > > I have several 100 users, none of them is able to install cygwin and > the packages they need the official way, they are way to *CENSORED* for > this job :-} If they can follow your current instructions, they can surely start some script that does this correctly? > 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") Whatever you call it, it's still cludgey nonsense that might or might not work. Only when it's not working your users will really be unable to figure out what to do since they won't even know what is failing. Again, to provide your tools properly for Cygwin, create a Cygwin package, set up a package repository that provides it and then start a script that calls setup to install it and any other packages you need (if not already installed by way of dependency). Setup can deal with multiple package repositories, so you can use one of the official mirrors as the primary package repository and only provide your package as an add-on repository (like cygwin ports does). Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables -- 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
Re: running self compiled 32 bit binary on 64 bit Windows?
On Mon 2018-07-09 (05:18), Andrey Repin wrote: > > 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. But I also need a test VM to check whether my self compiled programs will run on an other system. > > I have several 100 users, none of them is able to install cygwin > > *You* have to do it. No, I cannot do that. I do not have access to their PCs. > > 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 works so far without problems. > > Only by accident and promise. This is sufficent for me :-) -- Ullrich Horlacher Server und Virtualisierung Rechenzentrum TIK Universitaet Stuttgart E-Mail: horlac...@tik.uni-stuttgart.de Allmandring 30aTel:++49-711-68565868 70569 Stuttgart (Germany) WWW:http://www.tik.uni-stuttgart.de/ REF:<1124060518.20180709051...@yandex.ru> -- 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
Re: running self compiled 32 bit binary on 64 bit Windows?
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
Re: running self compiled 32 bit binary on 64 bit Windows?
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
Re: running self compiled 32 bit binary on 64 bit Windows?
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 > > 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 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. -- Ullrich Horlacher Server und Virtualisierung Rechenzentrum TIK Universitaet Stuttgart E-Mail: horlac...@tik.uni-stuttgart.de Allmandring 30aTel:++49-711-68565868 70569 Stuttgart (Germany) WWW:http://www.tik.uni-stuttgart.de/ REF:<49498971.20180608194...@yandex.ru> -- 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
Re: running self compiled 32 bit binary on 64 bit Windows?
Ulli Horlacher writes: > I have compiled the application with gcc from cygwin. You've compiled with the native compiler on a 32bit Cygwin, producing a 32bit Cygwin executable. > It runs without problems on Windows 7 32 bit but on Windows 8 64 bit it > does not output ANYTHING. No (error) message, nothing. You will either need to compile natively as a 64bit Cygwin executable, cross-compile to 64bit Cygwin, or target another cross-compiler at Windows 64bit or 32bit executables as you deem appropriate. In all cases any required runtime DLL need to be provided in the correct format as well. > How can I debug it? There is nothing to debug, this is simply not supposed to work. Before you ask, it doesn't work on Windows either (with 32bit Windows applications) unless the WoW64 subsystem is installed (it _almost_ always is, except in Core and Nano) nor would it work on Linux unless the 32bit loaders and libraries are installed. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Terratec KOMPLEXER: http://Synth.Stromeko.net/Downloads.html#KomplexerWaves -- 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
Re: running self compiled 32 bit binary on 64 bit Windows?
On Fri, Jun 8, 2018 at 3:45 PM, Ulli Horlacher wrote: > > There is no way to run a 32 bit cygwin binary on a 64 bit Windows system? There is, but you need a 32-bit Cygwin for that (which can be installed on 64-bit windows). Csaba -- You can get very substantial performance improvements by not doing the right thing. - Scott Meyers, An Effective C++11/14 Sampler So if you're looking for a completely portable, 100% standards-conformat way to get the wrong information: this is what you want. - Scott Meyers (C++TDaWYK) -- 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
Re: running self compiled 32 bit binary on 64 bit Windows?
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 adminNone 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 (0x7ffe0e52) >>> ??? => ??? (0x7733) >>> wow64.dll => /cygdrive/c/Windows/SYSTEM32/wow64.dll (0x772d) >>> wow64win.dll => /cygdrive/c/Windows/system32/wow64win.dll >>> (0x7726) >>> wow64cpu.dll => /cygdrive/c/Windows/system32/wow64cpu.dll >>> (0x7732) >> 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
Re: running self compiled 32 bit binary on 64 bit Windows?
Greetings, Ulli Horlacher! >> 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. >> 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 You have to install Cygwin, not "transfer". -- With best regards, Andrey Repin Friday, June 8, 2018 19:40:10 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
Re: running self compiled 32 bit binary on 64 bit Windows?
Greetings, Ulli Horlacher! >> -^^ >> THIS isn't 32bit Cygwin. >> >> You cannot run a 32bit Cygwin application under 64bit Cygwin. > This WAS my initial question! > There is no way to run a 32 bit cygwin binary ob a 64 bit Windows system? Cygwin is NOT Windows. Neither it is Linux, per se. > On Linux it is no problem, Ignorance is rarely an excuse, if ever. As I said previously, you have to transfer the cygwin1.dll of appropriate architecture to the host where you intend to run your application. Same for Linux. -- With best regards, Andrey Repin Friday, June 8, 2018 19:37:33 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
Re: running self compiled 32 bit binary on 64 bit Windows?
Keep the responses on list please. On 6/8/2018 9:45 AM, Ulli Horlacher wrote: > On Fri 2018-06-08 (09:37), cyg Simple wrote: >> On 6/8/2018 9:30 AM, Ulli Horlacher wrote: >> >> [-- TOFU entsorgt --] >> >> -^^ >> THIS isn't 32bit Cygwin. >> >> You cannot run a 32bit Cygwin application under 64bit Cygwin. > > This WAS my initial question! > > There is no way to run a 32 bit cygwin binary ob a 64 bit Windows system? > On Linux it is no problem, > You can only install a 32bit Cygwin on a 64bit Windows to execute a 32bit Cygwin application. You can execute 32bit Windows binaries on Windows 64bit as well. With Cygwin it is more difficult to segregate the appropriate libraries and the recommendation is to use two different environments if you need to still execute the 32bit software. But the better solution is to build it again. -- 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
Re: running self compiled 32 bit binary on 64 bit Windows?
On Fri 2018-06-08 (09:34), cyg Simple wrote: > On 6/8/2018 9:19 AM, Ulli Horlacher wrote: > > > > > I have compiled the application with gcc from cygwin. > > It runs without problems on Windows 7 32 bit but on Windows 8 64 bit it > > does not output ANYTHING. No (error) message, nothing. > > > > You CANNOT move a 32bit Cygwin application to a 64bit Cygwin > environment! It will not work. > > > How can I debug it? > > > > You can't! You need a 32bit Cygwin environment to run a 32bit application. > > The other option is to rebuild from source on the 64bit Cygwin. Ok, thanks for this illuminative answer! :-) -- Ullrich Horlacher Server und Virtualisierung Rechenzentrum TIK Universitaet Stuttgart E-Mail: horlac...@tik.uni-stuttgart.de Allmandring 30aTel:++49-711-68565868 70569 Stuttgart (Germany) WWW:http://www.tik.uni-stuttgart.de/ REF:<931f23f8-3b04-08fa-0e34-ed2aeab35...@gmail.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
RE: running self compiled 32 bit binary on 64 bit Windows?
Dear Ulli, > There is no way to run a 32 bit cygwin binary ob a 64 bit Windows system? You can easily install 32 bit Cygwin on 64 bit Windows (as I mentioned before). Best regards, Michael Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Christian Lamprechter Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -- 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
Re: running self compiled 32 bit binary on 64 bit Windows?
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' (0x37) 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' (0x37) 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' (0x37) 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: horlac...@tik.uni-stuttgart.de Allmandring 30aTel:++49-711-68565868 70569 Stuttgart (Germany) WWW:http://www.tik.uni-stuttgart.de/ REF:<0f7d3b1b3c4b894d824f5b822e3e5a17787fd...@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
Re: running self compiled 32 bit binary on 64 bit Windows?
On Fri 2018-06-08 (09:37), cyg Simple wrote: > On 6/8/2018 9:30 AM, Ulli Horlacher wrote: > > [-- TOFU entsorgt --] > > -^^ > THIS isn't 32bit Cygwin. > > You cannot run a 32bit Cygwin application under 64bit Cygwin. This WAS my initial question! There is no way to run a 32 bit cygwin binary ob a 64 bit Windows system? On Linux it is no problem, -- Ullrich Horlacher Server und Virtualisierung Rechenzentrum TIK Universitaet Stuttgart E-Mail: horlac...@tik.uni-stuttgart.de Allmandring 30aTel:++49-711-68565868 70569 Stuttgart (Germany) WWW:http://www.tik.uni-stuttgart.de/ REF:<0642bd66-ad0b-03b0-f5f9-226349cfd...@gmail.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
RE: running self compiled 32 bit binary on 64 bit Windows?
Dear Ulli, are you sure you want a cygwin build? I thought you are doing a MinGW build (since Cygwin1.ddl was missing from ldd). There are 3 possible ways: 1.) Do a MinGW cross compile in case you don't need any Cygwin infrastructure (bash, ...) or fully posix compliant C environment 2.) Do a Cygwin build and copy cygwin1.dll and possibly others with the executable in case you don't need a bash, but a posix compliant C environment. Depending on what DLLs you need, this might not work (some need some environment to run). 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 Best regards, Michael Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Christian Lamprechter Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -- 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
Re: running self compiled 32 bit binary on 64 bit Windows?
On Fri 2018-06-08 (15:30), Ulli Horlacher wrote: > Transfered to Windows 8 32 bit: Sorry, typo! It is Windows 8 64 bit! -- Ullrich Horlacher Server und Virtualisierung Rechenzentrum TIK Universitaet Stuttgart E-Mail: horlac...@tik.uni-stuttgart.de Allmandring 30aTel:++49-711-68565868 70569 Stuttgart (Germany) WWW:http://www.tik.uni-stuttgart.de/ REF:<20180608133017.gb20...@rus.uni-stuttgart.de> -- 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
Re: running self compiled 32 bit binary on 64 bit Windows?
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 adminNone 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 (0x7ffe0e52) > > ??? => ??? (0x7733) > > wow64.dll => /cygdrive/c/Windows/SYSTEM32/wow64.dll (0x772d) > > wow64win.dll => /cygdrive/c/Windows/system32/wow64win.dll > > (0x7726) > > wow64cpu.dll => /cygdrive/c/Windows/system32/wow64cpu.dll > > (0x7732) > > > > 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. -- Ullrich Horlacher Server und Virtualisierung Rechenzentrum TIK Universitaet Stuttgart E-Mail: horlac...@tik.uni-stuttgart.de Allmandring 30aTel:++49-711-68565868 70569 Stuttgart (Germany) WWW:http://www.tik.uni-stuttgart.de/ REF: -- 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
Re: running self compiled 32 bit binary on 64 bit Windows?
On 6/8/2018 9:30 AM, Ulli Horlacher wrote: > On Thu 2018-06-07 (01:04), Andrey Repin wrote: > >> Then I'm at a loss to explain the behavior. If he ran ldd on the same system >> he had built it (and where it is running properly), then there's >> environmental >> conditions involved. > > Windows 7 32 bit build system: > > /sw/cygwin-7_32/jed-0.99-20_116/bin: uname -a > CYGWIN_NT-6.1-WOW windoof 2.10.0(0.325/5/3) 2018-02-02 15:21 i686 Cygwin > > /sw/cygwin-7_32/jed-0.99-20_116/bin: ldd jed > ntdll.dll => /cygdrive/c/Windows/SysWOW64/ntdll.dll (0x76fb) > kernel32.dll => /cygdrive/c/Windows/syswow64/kernel32.dll (0x74af) > KERNELBASE.dll => /cygdrive/c/Windows/syswow64/KERNELBASE.dll > (0x7586) > cygslang-2.dll => /sw/cygwin-7_32/jed-0.99-20_116/bin/cygslang-2.dll > (0x6540) > cygwin1.dll => /usr/bin/cygwin1.dll (0x6100) > cyggcc_s-1.dll => /usr/bin/cyggcc_s-1.dll (0x6f90) > > Transfered to Windows 8 32 bit: > > /sw/cygwin-7_32/jed-0.99-20_116/bin: uname -a > CYGWIN_NT-6.3 W8-64 2.10.0(0.325/5/3) 2018-02-02 15:16 x86_64 Cygwin > -^^ THIS isn't 32bit Cygwin. You cannot run a 32bit Cygwin application under 64bit Cygwin. -- 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
Re: running self compiled 32 bit binary on 64 bit Windows?
On 6/8/2018 9:19 AM, Ulli Horlacher wrote: > > I have compiled the application with gcc from cygwin. > It runs without problems on Windows 7 32 bit but on Windows 8 64 bit it > does not output ANYTHING. No (error) message, nothing. > You CANNOT move a 32bit Cygwin application to a 64bit Cygwin environment! It will not work. > How can I debug it? > You can't! You need a 32bit Cygwin environment to run a 32bit application. The other option is to rebuild from source on the 64bit Cygwin. -- 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
Re: running self compiled 32 bit binary on 64 bit Windows?
On Thu 2018-06-07 (01:04), Andrey Repin wrote: > Then I'm at a loss to explain the behavior. If he ran ldd on the same system > he had built it (and where it is running properly), then there's environmental > conditions involved. Windows 7 32 bit build system: /sw/cygwin-7_32/jed-0.99-20_116/bin: uname -a CYGWIN_NT-6.1-WOW windoof 2.10.0(0.325/5/3) 2018-02-02 15:21 i686 Cygwin /sw/cygwin-7_32/jed-0.99-20_116/bin: ldd jed ntdll.dll => /cygdrive/c/Windows/SysWOW64/ntdll.dll (0x76fb) kernel32.dll => /cygdrive/c/Windows/syswow64/kernel32.dll (0x74af) KERNELBASE.dll => /cygdrive/c/Windows/syswow64/KERNELBASE.dll (0x7586) cygslang-2.dll => /sw/cygwin-7_32/jed-0.99-20_116/bin/cygslang-2.dll (0x6540) cygwin1.dll => /usr/bin/cygwin1.dll (0x6100) cyggcc_s-1.dll => /usr/bin/cyggcc_s-1.dll (0x6f90) Transfered to Windows 8 32 bit: /sw/cygwin-7_32/jed-0.99-20_116/bin: uname -a CYGWIN_NT-6.3 W8-64 2.10.0(0.325/5/3) 2018-02-02 15:16 x86_64 Cygwin /sw/cygwin-7_32/jed-0.99-20_116/bin: ldd jed ntdll.dll => /cygdrive/c/Windows/SYSTEM32/ntdll.dll (0x7ff880fa) ??? => ??? (0x7732) wow64.dll => /cygdrive/c/Windows/SYSTEM32/wow64.dll (0x772d) wow64win.dll => /cygdrive/c/Windows/system32/wow64win.dll (0x7726) wow64cpu.dll => /cygdrive/c/Windows/system32/wow64cpu.dll (0x7725) /sw/cygwin-7_32/jed-0.99-20_116/bin: ll /usr/bin/cygwin1.dll -rwxr-xr-x adminNone 3,195,569 2018-02-02 15:18:49 /usr/bin/cygwin1.dll -- Ullrich Horlacher Server und Virtualisierung Rechenzentrum TIK Universitaet Stuttgart E-Mail: horlac...@tik.uni-stuttgart.de Allmandring 30aTel:++49-711-68565868 70569 Stuttgart (Germany) WWW:http://www.tik.uni-stuttgart.de/ REF:<944481618.20180607010...@yandex.ru> -- 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
RE: running self compiled 32 bit binary on 64 bit Windows?
Dear Uli, in case you are not comfortable using gdb, Sysinternals ProcMon (can be downloaded for free from Microsoft) will give you information about what happens during process startup. Best regards, Michael Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Christian Lamprechter Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -- 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
Re: running self compiled 32 bit binary on 64 bit Windows?
On Wed 2018-06-06 (20:49), Andrey Repin wrote: > Greetings, Soegtrop, Michael! > > > Dear Ulli, > > > for MinGW (your ldd dump didn't include Cygwin dlls, so I assume you are > > doing MinGW builds) > > It did not include cygwin1.dll because he ran ldd on a system, where that > library was missing. May be you are right and he compiled it using > cross-compiler. I have compiled the application with gcc from cygwin. It runs without problems on Windows 7 32 bit but on Windows 8 64 bit it does not output ANYTHING. No (error) message, nothing. How can I debug it? -- Ullrich Horlacher Server und Virtualisierung Rechenzentrum TIK Universitaet Stuttgart E-Mail: horlac...@tik.uni-stuttgart.de Allmandring 30aTel:++49-711-68565868 70569 Stuttgart (Germany) WWW:http://www.tik.uni-stuttgart.de/ REF:<3110356010.20180606204...@yandex.ru> -- 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
Re: running self compiled 32 bit binary on 64 bit Windows?
Greetings, cyg Simple! >>> for MinGW (your ldd dump didn't include Cygwin dlls, so I assume you are >>> doing MinGW builds) >> >> It did not include cygwin1.dll because he ran ldd on a system, where that >> library was missing. May be you are right and he compiled it using >> cross-compiler. >> > Andrey, as I read the mail Ulli sent he showed that he was using Cygwin > so why wouldn't cygwin1.dll be shown if the app required it? Then I'm at a loss to explain the behavior. If he ran ldd on the same system he had built it (and where it is running properly), then there's environmental conditions involved. May be the explanation of build procedure drop some light. -- With best regards, Andrey Repin Thursday, June 7, 2018 1:03:05 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
Re: running self compiled 32 bit binary on 64 bit Windows?
On 6/6/2018 1:49 PM, Andrey Repin wrote: > Greetings, Soegtrop, Michael! > >> Dear Ulli, > >> for MinGW (your ldd dump didn't include Cygwin dlls, so I assume you are >> doing MinGW builds) > > It did not include cygwin1.dll because he ran ldd on a system, where that > library was missing. May be you are right and he compiled it using > cross-compiler. > Andrey, as I read the mail Ulli sent he showed that he was using Cygwin so why wouldn't cygwin1.dll be shown if the app required it? I often run non-cygwin apps in Cygwin and if there is a problem the pipes just don't get flushed correctly to display the data. To overcome this I start a cmd.exe window from my Cygwin shell, this leaves the environment set for the cmd.exe process. I then run the problem app and find the issue easily. -- 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
Re: running self compiled 32 bit binary on 64 bit Windows?
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@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 adminNone 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 (0x7ffe0e52) > ??? => ??? (0x7733) > wow64.dll => /cygdrive/c/Windows/SYSTEM32/wow64.dll (0x772d) > wow64win.dll => /cygdrive/c/Windows/system32/wow64win.dll (0x7726) > wow64cpu.dll => /cygdrive/c/Windows/system32/wow64cpu.dll (0x7732) > No mention of Cygwin in this list so you must have used a non-cygwin tool to build the package. > admin@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@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
Re: running self compiled 32 bit binary on 64 bit Windows?
Greetings, Soegtrop, Michael! > Dear Ulli, > for MinGW (your ldd dump didn't include Cygwin dlls, so I assume you are > doing MinGW builds) It did not include cygwin1.dll because he ran ldd on a system, where that library was missing. May be you are right and he compiled it using cross-compiler. > I would recommend to compile 32 bit binaries using a 32 > bit Cygwin (which can be installed on 64 bit machines). -- With best regards, Andrey Repin Wednesday, June 6, 2018 20:48:26 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
Re: running self compiled 32 bit binary on 64 bit Windows?
Greetings, Ulli Horlacher! > On Wed 2018-06-06 (19:02), Andrey Repin wrote: >> > On Windows 7 32 bit I have compiled some binaries by myself. >> > I can run them there but not on a Windows 8 64 bit: no (error) message, >> > nothing happens. >> >> >> > Do I have to install some 32 bit libs? >> >> Of course. Did you read the documentation or what? > Which documentation, where? Mind reading the mailing list signature once in a while? https://cygwin.com/docs.html >> > Which ones? >> >> cygwin1.dll at least. > In which package is this cygwin1.dll? In your /bin directory. >> Plus whatever API's your application is using. > Is there a command which tells which API/libs are used? ldd or cygcheck -- With best regards, Andrey Repin Wednesday, June 6, 2018 20:46:41 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
Re: running self compiled 32 bit binary on 64 bit Windows?
On Wed 2018-06-06 (19:02), Andrey Repin wrote: > > On Windows 7 32 bit I have compiled some binaries by myself. > > I can run them there but not on a Windows 8 64 bit: no (error) message, > > nothing happens. > > > > Do I have to install some 32 bit libs? > > Of course. Did you read the documentation or what? Which documentation, where? > > Which ones? > > cygwin1.dll at least. In which package is this cygwin1.dll? > Plus whatever API's your application is using. Is there a command which tells which API/libs are used? -- Ullrich Horlacher Server und Virtualisierung Rechenzentrum TIK Universitaet Stuttgart E-Mail: horlac...@tik.uni-stuttgart.de Allmandring 30aTel:++49-711-68565868 70569 Stuttgart (Germany) WWW:http://www.tik.uni-stuttgart.de/ REF:<41519955.20180606190...@yandex.ru> -- 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
RE: running self compiled 32 bit binary on 64 bit Windows?
Dear Ulli, sorry, I just saw that you did compile on a 32 bit Windows, so you had a 32 bit Cygwin - strange. What I can tell is that compiling a 32 bit app on a 32 bit Cygwin on a 64 bit Windows works and that such an app runs fine on 32 bit and 64 bit Windows. I test this regularly. I can't comment on how to compile something on a 32 bit Windows, I didn't do this in a while. Best regards, Michael Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Christian Lamprechter Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -- 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
RE: running self compiled 32 bit binary on 64 bit Windows?
Dear Ulli, for MinGW (your ldd dump didn't include Cygwin dlls, so I assume you are doing MinGW builds) I would recommend to compile 32 bit binaries using a 32 bit Cygwin (which can be installed on 64 bit machines). The reason is that the Windows file system has some hacks. Some DLLs are available as 32 bit and 64 bit versions under the same file name and path, and which version you get depends on if a 32 bit or 64 bit process accesses them. For this reason a linker which is a 64 bit process and tries to link 32 bit bianries gets the 64 bit versions of system DLLs. So in order to link 32 bit apps you need a linker which runs as a 32 bit process and for this you need a 32 bit Cygwin. The only other option (I know of) is to copy the required version of the required DLLs using a 32 bit or 64 bit copy program somewhere and tell the linker where to find them. Best regards, Michael Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Christian Lamprechter Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -- 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
Re: running self compiled 32 bit binary on 64 bit Windows?
Greetings, Ulli Horlacher! > On Windows 7 32 bit I have compiled some binaries by myself. > I can run them there but not on a Windows 8 64 bit: no (error) message, > nothing happens. > 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 adminNone 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 (0x7ffe0e52) > ??? => ??? (0x7733) > wow64.dll => /cygdrive/c/Windows/SYSTEM32/wow64.dll (0x772d) > wow64win.dll => /cygdrive/c/Windows/system32/wow64win.dll (0x7726) > wow64cpu.dll => /cygdrive/c/Windows/system32/wow64cpu.dll (0x7732) > > admin@WIN-7T5P92ALEEB:/sw/cygwin-7_32/jed-0.99-20_116/bin: ./jed > admin@WIN-7T5P92ALEEB:/sw/cygwin-7_32/jed-0.99-20_116/bin: > Do I have to install some 32 bit libs? Of course. Did you read the documentation or what? > Which ones? cygwin1.dll at least. Plus whatever API's your application is using. -- With best regards, Andrey Repin Wednesday, June 6, 2018 19:00:59 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
Re: running self compiled 32 bit binary on 64 bit Windows?
On 2018-06-06 13:50, Ulli Horlacher was heard to say: On Windows 7 32 bit I have compiled some binaries by myself. I can run them there but not on a Windows 8 64 bit: no (error) message, nothing happens. 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 adminNone 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 (0x7ffe0e52) ??? => ??? (0x7733) wow64.dll => /cygdrive/c/Windows/SYSTEM32/wow64.dll (0x772d) wow64win.dll => /cygdrive/c/Windows/system32/wow64win.dll (0x7726) wow64cpu.dll => /cygdrive/c/Windows/system32/wow64cpu.dll (0x7732) admin@WIN-7T5P92ALEEB:/sw/cygwin-7_32/jed-0.99-20_116/bin: ./jed admin@WIN-7T5P92ALEEB:/sw/cygwin-7_32/jed-0.99-20_116/bin: Do I have to install some 32 bit libs? Which ones? Why don't you just recompile th binaries on 64bit Cygwin? You seem to have the sources, so then... Markus -- Markus Hoenicka http://www.mhoenicka.de AQ score 38 -- 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
