1.7.14-2: Suspected lock-up in texlive-collection-basic post inst all when also installing CygwinPorts

[Moran, Christopher]

Hi

I am a newbie to the Cygwin mailing lists and have read through in detail
the process of reporting problems so hopefully I am submitting the following
problem to the correct mailing list. 

........

There appears to be a problem when installing Cygwin and CygwinPorts. I
followed the installation instructions at the following link, downloading
the files to a local drive before attempting the installation:
http://sourceware.org/cygwinports/
 
The MD5 checksums verified successfully, and all packages installed.
However, when running the post install script for texlive-collection-basic,
the installation process appeared to lock up: there was little CPU activity,
and although the installer was left running for several hours (overnight),
the texlive-collection-basic post install script did not finish.
 
I cancelled the installation and ran
/etc/postinstall/texlive-collection-basic.sh in a console window. It gave a
repeating sequence of the following two errors:
1 [main] perl 4920 child_info_fork::abort: unable to remap Fcntl.dll to same
address as parent (01FC0000) - try running rebaseall
1 [main] perl 5996 child_info_fork::abort: unable to remap MD5.dll to same
address as parent (01FB0000) - try running rebaseall This was surprising, as
rebaseall is the first thing run in post install (it is called from
/etc/postinstall/autorebase.bat). So a rebaseall would have been run just a
few moments before.
 
I did a little investigation on the web, and discovered that rebaseall does
not rebase perl modules:
http://cygwin.com/ml/cygwin/2012-02/msg00701.html
 
My solution was to force a rebase of the perl modules during the autorebase
post install process, by adding the following line to the end of
/etc/postinstall/autorebase.bat (in package _autorebase):
if exist bin\perlrebase sh /bin/perlrebase This change ensures that perl
modules are rebased before the texlive-collection-basic post install script
runs. This fixed the problem: Cygwin and CygwinPorts install successfully.
 
Cygwin and CygwinPorts were download on 1st May from a mirror (thus picking
up packages added or updated as of 30th April). The problem was verified on
two PCs, both running Windows XP Professional SP 3. The fix was verified on
the same two PCs.
 
......

Unfortunately I am not able to provide the output from the command cygcheck
as it contains sensitive information.

If you require any further information then please don't hesitate to contact
me.

Best Regards

Chris Moran

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