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

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' (0x370000) 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' (0x370000) 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' (0x370000) is already occupied
   Can't fork, trying again in 5 seconds at /client/bin/fexsend line 106.

See my mail:

From: Ulli Horlacher <framstag@rus.uni-stuttgart.de>
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: horlacher@tik.uni-stuttgart.de
Allmandring 30a                Tel:    ++49-711-68565868
70569 Stuttgart (Germany)      WWW:    http://www.tik.uni-stuttgart.de/
REF:<0F7D3B1B3C4B894D824F5B822E3E5A17787FD684@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

  reply	other threads:[~2018-06-08 13:52 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 [this message]
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=20180608135221.GF20898@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).