public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Soegtrop, Michael" <michael.soegtrop@intel.com>
To: Ulli Horlacher <framstag@rus.uni-stuttgart.de>,
	"cygwin@cygwin.com"	<cygwin@cygwin.com>
Subject: RE: running self compiled 32 bit binary on 64 bit Windows?
Date: Fri, 08 Jun 2018 13:43:00 -0000	[thread overview]
Message-ID: <0F7D3B1B3C4B894D824F5B822E3E5A17787FD684@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <20180608133017.GB20898@rus.uni-stuttgart.de>

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

  parent reply	other threads:[~2018-06-08 13:43 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 [this message]
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
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=0F7D3B1B3C4B894D824F5B822E3E5A17787FD684@IRSMSX102.ger.corp.intel.com \
    --to=michael.soegtrop@intel.com \
    --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).