X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=3.4 required=5.0 tests=AWL,BAYES_40,RCVD_IN_DNSWL_NONE
X-Spam-Check-By:	sourceware.org
Message-Id:	<201203192105.q2JL5Guv026181@telford.daku.org>
Date:	Mon, 19 Mar 2012 14:02:33 -0700
To:	cygwin AT cygwin DOT com
From:	david <david AT daku DOT org>
Subject:	Setup 1.7.11 texlive postinstall takes 6+ hours
Mime-Version:	1.0
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

I have noticed that the postinstall processing of "texlive" seems to 
go on for hours, even on a reasonably powerful computer (Intel i7, 
64bit, 2.5G memory running Windows 7 in VirtualBox (host Centos6) 
with 5 cores).  I am running a fresh install using Cygwin Setup 
1.7.11-1 on an otherwise empty system.  This delay was not true in 
1.7.9; it ran to completion in reasonable time.

For the past few days, I've actually aborted the install several 
times because I thought it was hung.  By "forever" I mean 6+ hours of 
solid compute with occasional disk activity as it runs through 
"texlive-collection-lang-*" language by language.  Had I not let it 
run overnight, I don't think I would have ever concluded that it 
would ever finish.  No other VM is active, and the underlying Linux 
is quiet too.

Is this really necessary?  I could of course omit TeX, but that's not 
a good solution.

David


--
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

- Raw text -