From: "KARR, DAVID" <dk068x@att.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: New cygwin install hanging on postinstall
Date: Thu, 21 Jan 2016 19:09:00 -0000 [thread overview]
Message-ID: <B8D164BED956C5439875951895CB4B2250BB0354@CAFRFD1MSGUSRJH.ITServices.sbc.com> (raw)
In-Reply-To: <CANnLRdi5sqTnOmen7oufLFJEi+wZX4BuGpfD58Wf8i7=NfEt9Q@mail.gmail.com>
> -----Original Message-----
> From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com] On
> Behalf Of Stephen John Smoogen
> Sent: Wednesday, January 20, 2016 4:19 PM
> To: cygwin@cygwin.com
> Subject: Re: New cygwin install hanging on postinstall
>
> On 20 January 2016 at 17:06, KARR, DAVID <dk068x@att.com> wrote:
> > I was installing cygwin for the first time on a Win7-32bit box.
> It is hanging in postinstall, with "0/Perpetual" and
> "/etc/postinstall/0p_texlive_prep.dash. I've tried this twice now,
> and it hangs effectively forever on this step (waited 15-20 minutes
> each time). What other information could I provide? I looked at
> the end of the setup.log file, but that just indicates that
> installation was complete.
> >
>
> How much memory does this system have? I know that TexLive is a
> real
> memory hog these days in certain parts.. Does removing TexLive from
> your install list go past this?
It has 4g RAM. Checking "Resource Monitor" while the install is running, there is 750MB "available".
I tried searching for "texlive" and setting all of those to "uninstall". The "postintall" step spends quite a while on "0p_000_autorebase.dash", but I noticed that before. However, after that finishes, it then sits on "0p_texlive_prep.dash".
While it's sitting here, I dumped out "/var/log/setup.log.full". Here is the end of the file:
----------------
The following DLLs couldn't be rebased because they were in use:
/usr/bin/cygssp-0.dll
/usr/bin/cygperl5_22.dll
/usr/bin/cyggcc_s-1.dll
/usr/bin/cygcrypt-0.dll
/usr/lib/perl5/vendor_perl/5.22/i686-cygwin-threads-64int/auto/List/Util/Util.
dll
/usr/lib/perl5/5.22/i686-cygwin-threads-64int/auto/IO/IO.dll
/usr/lib/perl5/5.22/i686-cygwin-threads-64int/auto/File/Glob/Glob.dll
/usr/lib/perl5/5.22/i686-cygwin-threads-64int/auto/Fcntl/Fcntl.dll
/usr/lib/perl5/5.22/i686-cygwin-threads-64int/auto/Encode/Encode.dll
/usr/lib/perl5/5.22/i686-cygwin-threads-64int/auto/Digest/MD5/MD5.dll
/usr/lib/perl5/5.22/i686-cygwin-threads-64int/auto/Cwd/Cwd.dll
2016/01/21 09:15:40 running: C:\cygwin\bin\dash.exe "/etc/postinstall/0p_texlive
_prep.dash"
2016/01/21 09:19:20 note: Nothing needed to be installed
2016/01/21 09:19:20 Ending cygwin install
-----------
Note that the current time is currently 9:37AM. The log file hasn't updated in almost 20 minutes.
I would run the script manually, but I don't know what to run.
I tried to exclude c:\cygwin from the virus scanner, but it seems doubtful that the installer would go through all the other steps if this was really an issue.
next prev parent reply other threads:[~2016-01-21 17:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 5:34 KARR, DAVID
2016-01-21 5:42 ` Stephen John Smoogen
2016-01-21 19:09 ` KARR, DAVID [this message]
2016-01-21 21:29 ` Ken Brown
2016-01-21 21:51 ` Achim Gratz
2016-01-22 3:12 ` KARR, DAVID
2016-01-22 7:30 ` David Stacey
2016-01-22 17:32 ` Andrey Repin
2016-01-22 18:50 ` KARR, DAVID
2016-01-22 20:07 ` Mark Geisert
2016-01-22 20:14 ` Andrey Repin
2016-01-21 8:02 ` Ken Brown
2016-01-21 13:18 ` Achim Gratz
2016-01-21 21:17 ` Ken Brown
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=B8D164BED956C5439875951895CB4B2250BB0354@CAFRFD1MSGUSRJH.ITServices.sbc.com \
--to=dk068x@att.com \
--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).