bug-make
[Top][All Lists]
Advanced

[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: Andreas K. Hüttel
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:06:11 -0400 (EDT)

URL:
  <https://savannah.gnu.org/bugs/?64664>

                 Summary: what could cause make to stop with "make[3]: ***
wait: No such file or directory.  Stop."
                   Group: make
               Submitter: dilfridge
               Submitted: Thu 14 Sep 2023 01:06:09 AM CEST
                Severity: 3 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
       Component Version: 4.4.1
        Operating System: POSIX-Based
           Fixed Release: None
           Triage Status: None


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Thu 14 Sep 2023 01:06:09 AM CEST By: Andreas K. Hüttel <dilfridge>
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 harmless)

* Sometimes, programs that should build perfectly (gcc, binutils) stop with a
message:
make[3]: Leaving directory
'/var/tmp/portage/sys-devel/gcc-13.2.1_p20230826/work/build/libiberty'
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
MAKEOPTS="-j1"

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...

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 this)







    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?64664>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/




reply via email to

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