From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Cygwin 2.6.1 32-bit post install failed by /usr/bin/perl.exe
Date: Mon, 16 Jan 2017 17:58:00 -0000 [thread overview]
Message-ID: <871sw2evkw.fsf@Rainer.invalid> (raw)
In-Reply-To: <b4mshojsbt1.fsf@jpl.org> (Katsumi Yamaoka's message of "Mon, 16 Jan 2017 16:28:58 +0900")
Katsumi Yamaoka writes:
> Run setup-x86.exe for full install excluding *x86_64* modulues.
You do not want a full Cygwin install. In particular, you do not want a
full installl for Cygwin 32bit.
> However, the post install didn't seem to end. At that time, ps
> on mintty showed a lot of defunct perl processes. Then I tried
> replacing /usr/bin/perl.exe with the one I built from the source
> one and a half years ago.
You've run out of address space to rebase to and now perl (which comes
pretty late in the rebase sequence) collides with something else on your
system or maybe even the Cygwin heap.
> It did the trick! Now new cygwin is running with no problem!
No it doesn't and it never will given that you did a full install.
Please do a fresh install with only the packages that you need. If you
select too many packages you will likely need to switch to a 3GB
userVM address space even then. You are much better off using a 64bit
Cygwin if you're using a 64bit Windows version.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
--
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:[~2017-01-16 17:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 7:29 Katsumi Yamaoka
2017-01-16 17:58 ` Achim Gratz [this message]
2017-01-18 1:02 ` Katsumi Yamaoka
2017-01-18 18:21 ` Achim Gratz
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=871sw2evkw.fsf@Rainer.invalid \
--to=stromeko@nexgo.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).