Mention 64-bit Cygwin as another remedy for fork() failures.
This commit is contained in:
parent
2cd76694e1
commit
bf45e12fb6
|
@ -1394,13 +1394,15 @@ such as virtual memory paging and file caching.</para>
|
|||
<para><itemizedlist>
|
||||
<listitem>Restart whatever process is trying (and failing) to use
|
||||
<literal>fork()</literal>. Sometimes Windows sets up a process
|
||||
environment that is even more hostile to fork() than usual.</listitem>
|
||||
environment that is even more hostile to <literal>fork()</literal> than usual.</listitem>
|
||||
<listitem>Ensure that you have eliminated (not just disabled) all
|
||||
software on the <xref linkend="faq.using.bloda"/>.
|
||||
</listitem>
|
||||
<listitem>Read the 'rebase' package README in
|
||||
<literal>/usr/share/doc/rebase/</literal>, and follow the
|
||||
instructions there to run 'rebaseall'.</listitem>
|
||||
<listitem>Switch from 32-bit Cygwin to 64-bit Cygwin, if your OS and CPU support that.
|
||||
With the bigger address space <literal>fork()</literal> is less likely to fail.</listitem>
|
||||
</itemizedlist></para>
|
||||
<para>Please note that installing new packages or updating existing
|
||||
ones undoes the effects of rebaseall and often causes fork() failures
|
||||
|
|
Loading…
Reference in New Issue