Cygwin error: "child_info_fork :: abort: loaded to another address:"

Question

I am trying to build my software using cygwin-x86 (32-bit) on Windows-7.
Cygwin-x64 (64 bit) works fine on one machine. I want to build a 32 bit executable.
Whenever I try cygwin-x86, I get the following errors:

[main] make 7780 child_info_fork :: abort: C: \ cygwin \ bin \ cygiconv-2.dll: loaded to another address: parent (0x440000)! = child (0x5F0000)
do: fork: the resource is temporarily unavailable

I checked this thread Cygwin Error

I already tried everything that was mentioned there, but I still continue to face the same problem.
Whenever I try to use / usr / bin / rebaseall -v or cd / usr / bin && &. / Rebaseall -v , as indicated in step 7 of the accepted answer in the above thread, I get this error:

/usr/x86_64-pc-cygwin/sys-root/usr/bin/cygvtv_stubs-0.dll: skipped because the wrong machine type. / usr / x 86_64-pc-cygwin / sys-root / usr / bin / cygz.dll: skipped because the device type is incorrect.
Segmentation error (kernel flushing)

I get this error of the wrong machine type for many other .dlls.
As mentioned earlier, I have cygwin-64 installed on my machine and working as expected. But when starting rebaseall, it somehow looks for x86-64-pc-cygwin instead of the 32-bit version.

Answer 1

This thread is out of date.

run /usr/bin/rebase-trigger , close all cygwin processes and run setup-x86.exe . Also, without installation, nothing will rebase for you.

You can also specify the complete option.

Note: The most likely cause of problems with fork on a 32-bit system is too many programs and libraries.

for example: /usr/x86_64-pc-cygwin/sys-root/usr/bin/cygz.dll

belongs to the cygwin64-zlib cross-library for creating cygwin64 programs from cygwin32. Do you really need this? If not, as I suspect, remove all cywgin64 packages.

Answer 2

The problem can also be caused by an antivirus program. (I saw this happening with Avast.) You can check if this is the cause by disabling it.

Answer 3

You can also kill each of the last ash, dash or bash processes that have been forked, setup.exe will simply skip this script and continue working with the rest. I had to kill about 10-20 of them, mainly in latex postinstall scripts.

Answer 4

I had the same problem. I solved this by restarting the computer.