* Deadlock in build process? (make -j used)
@ 2018-06-16 10:54 U.Mutlu
2018-06-17 12:08 ` Deadlock in build process? (make -j used) [SOLVED} U.Mutlu
0 siblings, 1 reply; 2+ messages in thread
From: U.Mutlu @ 2018-06-16 10:54 UTC (permalink / raw)
To: gcc
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Deadlock in build process? (make -j used) [SOLVED}
2018-06-16 10:54 Deadlock in build process? (make -j used) U.Mutlu
@ 2018-06-17 12:08 ` U.Mutlu
0 siblings, 0 replies; 2+ messages in thread
From: U.Mutlu @ 2018-06-17 12:08 UTC (permalink / raw)
To: gcc
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2018-06-16 10:54 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-06-16 10:54 Deadlock in build process? (make -j used) U.Mutlu
2018-06-17 12:08 ` Deadlock in build process? (make -j used) [SOLVED} U.Mutlu
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).