From: Katsumi Yamaoka <yamaoka@jpl.org>
To: cygwin@cygwin.com
Subject: Re: Cygwin 2.6.1 32-bit post install failed by /usr/bin/perl.exe
Date: Wed, 18 Jan 2017 01:02:00 -0000 [thread overview]
Message-ID: <b4mpojluqon.fsf@jpl.org> (raw)
In-Reply-To: <871sw2evkw.fsf@Rainer.invalid>
On Mon, 16 Jan 2017 18:57:51 +0100, Achim Gratz wrote:
> 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.
Yes, I know I overdo or am greedy. So, I tried minimal install,
that is:
Stop cygwin
cd c:\
ren cygwin cygwin.cur
Run setup-x86.exe with the default configuration, plus Emacs,
Perl, X11, and some required dependencies.
It finished with no problem and main commands work fine. Oh!
>> 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.
I see. But the current 32-bit full-install seems to work (I
haven't tested everything, though). Does it mean only a space,
that is comparable to the one perl and possibly a few modules
occupy, exceeds the limit? Moreover, is there no way to know
how many space exceeds the limit, before installing? I won't do
it even if it exists if it is hard to me, though.
Anyway, it's handy that everything is close at hand. ;)
>> 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.
Ok, I will try negotiating with boss for a 64-bit machine at the
next opportunity. This is an office pc.
Thank you very much for your help.
Regards,
--
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-18 1:02 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
2017-01-18 1:02 ` Katsumi Yamaoka [this message]
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=b4mpojluqon.fsf@jpl.org \
--to=yamaoka@jpl.org \
--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).