From: Ulli Horlacher <framstag@rus.uni-stuttgart.de>
To: cygwin@cygwin.com
Subject: Re: running self compiled 32 bit binary on 64 bit Windows?
Date: Mon, 09 Jul 2018 06:29:00 -0000 [thread overview]
Message-ID: <20180709062947.GC3525@rus.uni-stuttgart.de> (raw)
In-Reply-To: <1124060518.20180709051834@yandex.ru>
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: horlacher@tik.uni-stuttgart.de
Allmandring 30a Tel: ++49-711-68565868
70569 Stuttgart (Germany) WWW: http://www.tik.uni-stuttgart.de/
REF:<1124060518.20180709051834@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
next prev parent reply other threads:[~2018-07-09 6:29 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 ` Ulli Horlacher
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
2018-07-09 6:22 ` Brian Inglis
2018-07-09 6:29 ` Ulli Horlacher [this message]
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: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=20180709062947.GC3525@rus.uni-stuttgart.de \
--to=framstag@rus.uni-stuttgart.de \
--cc=cygwin@cygwin.com \
/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).