This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: New cygwin install hanging on postinstall
- From: Achim Gratz <Stromeko at nexgo dot de>
- To: cygwin at cygwin dot com
- Date: Thu, 21 Jan 2016 21:10:27 +0100
- Subject: Re: New cygwin install hanging on postinstall
- Authentication-results: sourceware.org; auth=none
- References: <B8D164BED956C5439875951895CB4B2250BAE63C at CAFRFD1MSGUSRJH dot ITServices dot sbc dot com> <CANnLRdi5sqTnOmen7oufLFJEi+wZX4BuGpfD58Wf8i7=NfEt9Q at mail dot gmail dot com> <B8D164BED956C5439875951895CB4B2250BB0354 at CAFRFD1MSGUSRJH dot ITServices dot sbc dot com>
KARR, DAVID writes:
> 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
> -----------
So this isn't a fresh install and in fact there is not only some Cygwin
process running but a full blown Perl that has loaded a number of
modules. How'd you manage to do that before Cygwin was ready
installing? Are you perhaps reporting from a follow-on invocation of
setup.exe after the first install already failed?
For your current case, you need to get rid of _all_ running Cygwin
processes. Best idea is to open a shell and issue
/usr/bin/rebase-trigger fullrebase
/usr/bin/pkill .
(you need to have procps installed for this command to be available).
Then run setup again to have it re-do the rebase and run all postinstall
scripts that failed before. But I'm still interested how that initial
failure could have occured, so if you could maybe look in
/var/log/setup.log if something indicates what happened there that would
be good.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
--
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