From: Andrey Repin <anrdaemon@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?
Date: Mon, 09 Jul 2018 02:20:00 -0000 [thread overview]
Message-ID: <1124060518.20180709051834@yandex.ru> (raw)
In-Reply-To: <20180709002131.GA3525@rus.uni-stuttgart.de>
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
next prev parent reply other threads:[~2018-07-09 2:20 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 11:50 Ulli Horlacher
2018-06-06 12:05 ` Markus Hoenicka
2018-06-06 16:05 ` Andrey Repin
2018-06-06 16:42 ` Ulli Horlacher
2018-06-06 17:50 ` Andrey Repin
2018-06-06 16:25 ` Soegtrop, Michael
2018-06-06 16:29 ` Soegtrop, Michael
2018-06-06 17:50 ` Andrey Repin
2018-06-06 20:26 ` cyg Simple
2018-06-06 22:05 ` Andrey Repin
2018-06-08 13:31 ` Ulli Horlacher
2018-06-08 13:37 ` cyg Simple
2018-06-08 13:45 ` Ulli Horlacher
2018-06-08 13:52 ` Soegtrop, Michael
2018-06-08 13:56 ` cyg Simple
2018-06-08 16:50 ` Andrey Repin
2018-06-08 18:20 ` Csaba Raduly
2018-06-08 13:43 ` Soegtrop, Michael
2018-06-08 13:52 ` Ulli Horlacher
2018-06-08 16:50 ` Andrey Repin
2018-07-09 0:21 ` Ulli Horlacher
2018-07-09 2:20 ` Andrey Repin [this message]
2018-07-09 6:22 ` Brian Inglis
2018-07-09 6:29 ` Ulli Horlacher
2018-07-14 15:41 ` Achim Gratz
2018-08-17 10:29 ` distributing preconfigured cygwin (was: running self compiled 32 bit binary on 64 bit Windows?) Ulli Horlacher
2018-08-17 10:58 ` distributing preconfigured cygwin john doe
2018-08-17 17:05 ` distributing preconfigured cygwin (was: running self compiled 32 bit binary on 64 bit Windows?) Andrey Repin
2018-08-17 19:49 ` distributing preconfigured cygwin Achim Gratz
2018-08-29 11:09 ` Ulli Horlacher
2018-08-29 11:31 ` Andrey Repin
2018-08-29 12:08 ` john doe
2018-08-30 12:35 ` running self compiled 32 bit binary on 64 bit Windows? Ulli Horlacher
2018-08-30 13:55 ` Marco Atzeri
2018-08-30 13:59 ` Andrey Repin
2018-08-30 19:20 ` Ulli Horlacher
2018-08-30 21:06 ` Ulli Horlacher
2018-08-31 8:58 ` Andrey Repin
2018-08-31 8:35 ` Achim Gratz
2018-06-08 13:43 ` Ulli Horlacher
2018-06-08 13:19 ` Ulli Horlacher
2018-06-08 13:28 ` Soegtrop, Michael
2018-06-08 13:34 ` cyg Simple
2018-06-08 13:54 ` Ulli Horlacher
2018-06-08 19:05 ` Achim Gratz
2018-06-06 20:13 ` cyg Simple
2018-06-08 13:42 ` Ulli Horlacher
2018-06-08 17:44 ` Brian Inglis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1124060518.20180709051834@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=framstag@rus.uni-stuttgart.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).