From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Fork issue on W10 WOW
Date: Sun, 01 Jul 2018 08:51:00 -0000 [thread overview]
Message-ID: <1f9a4621-6e2a-6640-fb4c-f10ccf1135ce@gmail.com> (raw)
In-Reply-To: <c1505248-8d03-c0b6-37ca-9c6eed2100e9@cornell.edu>
Am 30.06.2018 um 22:47 schrieb Ken Brown:
> On 6/30/2018 11:52 AM, Marco Atzeri wrote:
>> Hi,
>> on a new W10 HP Laptop, the 32 bit installation always fails
>> on postinstallation scripts that use perl.
>>
>> The outcome is like:
>>
>> $ ./texlive-collection-formatsextra.sh
>> Â Â Â Â Â Â 1 [main] perl 1796 child_info_fork::abort: address space needed
>> by 'Encode.dll' (0x2620000) is already occupied
>> Can't fork, trying again in 5 seconds at /usr/bin/fmtutil line 73.
>>
> [...]
>> Until I have the 32bit running I can not deploy any new package, as
>> the previous W7 is retired.
>
> I've never had this problem with my own 32bit installation on W10, but I
> just reproduced it by doing a new installation with your list of
> packages. Have you tried just installing a minimal list of packages
> that you need for building the packages you maintain?
partially tried, and the minimal installation was fine.
> Alternatively, you might work around the problem by first doing a base
> install, then installing your texlive-collection-* packages, and then
> installing everything else. I just tested this with your list of
> packages, and it worked for me.
I will give a try to this sequence.
> Ken
Thanks for your experiment
Marco
---
Diese E-Mail wurde von AVG auf Viren geprüft.
http://www.avg.com
--
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:[~2018-07-01 8:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-30 17:33 Marco Atzeri
[not found] ` <c1505248-8d03-c0b6-37ca-9c6eed2100e9@cornell.edu>
2018-07-01 8:51 ` Marco Atzeri [this message]
2018-07-08 16:03 ` Marco Atzeri
2018-07-09 9:03 ` Corinna Vinschen
2018-07-09 11:37 ` Marco Atzeri
2018-07-09 12:37 ` Corinna Vinschen
2018-07-10 5:33 ` Marco Atzeri
2018-07-12 12:34 ` marco atzeri
2018-07-14 12:46 ` Corinna Vinschen
2018-07-14 14:31 ` Marco Atzeri
2018-07-14 17:58 ` Achim Gratz
2018-07-14 19:03 ` Marco Atzeri
2018-07-14 22:41 ` Achim Gratz
2018-07-15 2:12 ` Brian Inglis
2018-07-15 9:18 ` Marco Atzeri
2018-07-15 13:25 ` Achim Gratz
2018-07-15 19:33 ` Brian Inglis
2018-07-15 23:01 ` David Stacey
2018-07-16 18:58 ` Marco Atzeri
2018-07-16 1:06 ` Andrey Repin
2018-07-17 18:34 ` Marco Atzeri
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=1f9a4621-6e2a-6640-fb4c-f10ccf1135ce@gmail.com \
--to=marco.atzeri@gmail.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).