Re: ct-ng build hangs forever

[Claude <claude@cbcr.me>]

Thomas Petazzoni <thomas.petazzoni <at> free-electrons.com> writes:

> 
> 
> When the thing is eating 100% cpu and stuck, can you do a "ps auxf",
> and give the output of the process tree that starts from the ct-ng
> process? This way, we would see which thing is actually stuck. That
> might help in giving a clue.
> 

Here it is


     11933 10632             make -f ct-ng build
     11947 11933             /bin/bash /home
  /ct-ng.1.19.0/scripts/crosstool-NG.sh
     16920 11947               /bin/bash /home
  /ct-ng.1.19.0/scripts/crosstool-NG.sh
     16933 16920                 /bin/bash /home
 /ct-ng.1.19.0/scripts/crosstool-NG.sh
     16937 16933                   /bin/bash /home
 /crosstool-ng-1.19.0/.build/src/gmp-4.3.2/configure
 --no-reexec --build=x86
     17266 16937                     /bin/bash /home
 /crosstool-ng-1.19.0/.build/src/gmp-4.3.2/configure
 --no-reexec --build=x
     17267 17266                       /bin/bash /home
 /crosstool-ng-1.19.0/.build/tools/bin/make
 -j 4 -j 4 -j 4 -j 4 -j 4 -j
     16938 16933                   /bin/bash
 /home/ct-ng.1.19.0/scripts/crosstool-NG.sh
     16939 16938                     /bin/bash
 /home/b /ct-ng.1.19.0/scripts/crosstool-NG.sh
     16942 16939                       cat -
     16940 16938                     /bin/bash
 /home/ /ct-ng.1.19.0/scripts/crosstool-NG.sh



I removed some of the column because of the 80 character limit on this
post system. I also cut the command line pathname.  The process ID that
was running 100% is 17267. Bizarre that there is no child.

Using htop I looked at the command line of that PID, the -j 4 reports
ad nauseam for very very very long. In a previous run, I did
configure ct to use only 1 core but the -j 4 was still there.

I call ct-ng using make since the first line, containing #!make,
does not work, unless I modify it to include the full path of make






--
For unsubscribe information see http://sourceware.org/lists.html#faq