[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #64664] what could cause make to stop with "make[3]: *** wait: No s

From: Alejandro Colomar
Subject: [bug #64664] what could cause make to stop with "make[3]: *** wait: No such file or directory. Stop."
Date: Wed, 13 Sep 2023 19:25:22 -0400 (EDT)

Follow-up Comment #1, bug #64664 (project make):

Hi Andreas,

[comment #0 original submission:]
> This is not so much a bug report as a call for help...
> I'm trying to get Gentoo ported onto riscv32 using qemu usermode. Something
is wrong... my chroot is ~90% functional, but a few programs behave erratic,
among them bash (!) and make.
> I observe two oddities with make.
> * It seems to always only start one job no matter -j9 (annoying but
> * Sometimes, programs that should build perfectly (gcc, binutils) stop with
a message:
> make[3]: Leaving directory
> make[4]: Nothing to be done for 'all'.
> make[3]: *** wait: No such file or directory.  Stop.
> make[3]: *** Waiting for unfinished jobs....
> I seem to remember that I can circumvent this ^ by explicitly saying
> Now, these are most likely *not* make bugs. 
> However, any advice what in one of the underlying layers (glibc, qemu) might
be failing would be very much appreciated...

I think it's failing here:


But it's failing with ENOENT, which is not one of the documented errors for

     EAGAIN The PID file descriptor specified in id  is  nonblocking  and 
            process that it refers to has not terminated.

     ECHILD (for  wait())  The  calling process does not have any

     ECHILD (for waitpid() or waitid()) The process specified  by  pid 
            pid())  or  idtype  and  id  (waitid()) does not exist or is not
            child of the calling process.  (This  can  happen  for  one’s 
            child  if  the action for SIGCHLD is set to SIG_IGN.  See also
            Linux Notes section about threads.)

     EINTR  WNOHANG was not set and an  unblocked  signal  or  a  SIGCHLD 
            caught; see signal(7).

     EINVAL The options argument was invalid.

     ESRCH  (for wait() or waitpid()) pid is equal to INT_MIN.

But I guess it's related to the inability to start more than one process.
Maybe it thinks it has started more processes, and tries to wait for them,
but there are no such entries?


> See also:
> https://lists.gnu.org/archive/html/bug-bash/2023-09/msg00119.html
> https://lists.gnu.org/archive/html/qemu-devel/2023-09/msg02894.html
> (the qemu patch by LIU Zhiwei seems to make no difference, just testing


Reply to this item at:


Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]