Deadlock in build process? (make -j used) [SOLVED}

U.Mutlu um@mutluit.com
Sun Jun 17 12:08:00 GMT 2018


It seems this was caused by not having enough free-space on /tmp.
Increasing it to 3GB solved the problem.
Btw, my /tmp is a ramdisk, ie. tmpfs.


U.Mutlu wrote on 06/16/2018 09:20 AM:
> Not sure if the following is just a coincidence, but happened lately
> each of the two times I started the build process (make -j8) without
> previously giving the --disable-bootstrap parameter to the configure command:
>
> /bin/bash ../../gcc_trunk/gcc/lock-and-run.sh linkfe.lck ...
> waiting to acquire linkfe.lck
> waiting to acquire linkfe.lck
> waiting to acquire linkfe.lck
> waiting to acquire linkfe.lck
> waiting to acquire linkfe.lck
> waiting to acquire linkfe.lck
> waiting to acquire linkfe.lck
> waiting to acquire linkfe.lck
> waiting to acquire linkfe.lck
> waiting to acquire linkfe.lck
> waiting to acquire linkfe.lck
> waiting to acquire linkfe.lck
> waiting to acquire linkfe.lck
> waiting to acquire linkfe.lck
> waiting to acquire linkfe.lck
> waiting to acquire linkfe.lck
> waiting to acquire linkfe.lck
> waiting to acquire linkfe.lck
> waiting to acquire linkfe.lck
> ^C
>
> It fills up /tmp and aborts with error and leaves /tmp full with countless
> temporary cc* files.
> Since my /tmp is mounted and is limited to just 1.1GB, here I did Ctrl-C.
> Btw, --enable-link-mutex was/is in effect.



More information about the Gcc mailing list