Project

General

Profile

Actions

Bug #21676

open

make[2]: *** No rule to make target '../../../.././ext/-test-/namespace/yay1/yay1.h', needed by 'yay1.o'. Stop.

Bug #21676: make[2]: *** No rule to make target '../../../.././ext/-test-/namespace/yay1/yay1.h', needed by 'yay1.o'. Stop.

Added by duerst (Martin Dürst) 23 days ago. Updated 19 days ago.

Status:
Open
Assignee:
-
Target version:
-
ruby -v:
ruby 3.5.0dev (2025-11-02T10:22:22Z master bd51b20c50) +PRISM [x86_64-linux] last_commit=minor code allignment (related to bug 21559)
[ruby-core:123738]

Description

When I tried to compile Ruby with make up; make, I got the message in the Subject.
This seems similar to bug #19481, but the various kinds of advice (./config.status or ./autogen.sh; ./configure; make) given there didn't solve the problem.

The last part of the output is

compiling memory_view.c
linking shared-object -test-/memory_view.so
make[2]: Leaving directory '/home/duerst/34ruby/ext/-test-/memory_view'
make[2]: Entering directory '/home/duerst/34ruby/ext/-test-/method'
compiling arity.c
compiling init.c
linking shared-object -test-/method.so
make[2]: Leaving directory '/home/duerst/34ruby/ext/-test-/method'
make[2]: Entering directory '/home/duerst/34ruby/ext/-test-/namespace/yay1'
make[2]: *** No rule to make target '../../../.././ext/-test-/namespace/yay1/yay1.h', needed by 'yay1.o'.  Stop.
make[2]: Leaving directory '/home/duerst/34ruby/ext/-test-/namespace/yay1'
make[1]: *** [exts.mk:197: ext/-test-/namespace/yay1/all] Error 2
make[1]: Leaving directory '/home/duerst/34ruby'
make: *** [uncommon.mk:351: build-ext] Error 2

Updated by nagachika (Tomoyuki Chikanaga) 23 days ago Actions #1 [ruby-core:123743]

I just run into the same problem now.
In my environment, removing exts.mk in build directory resolved the issue.

Updated by nobu (Nobuyoshi Nakada) 23 days ago 1Actions #2 [ruby-core:123744]

Yes, it is a known issue.
It is possible to avoid by comparing the extension library path list each time, but moving extension library path is quite rare case.

Updated by duerst (Martin Dürst) 22 days ago Actions #3 [ruby-core:123751]

nagachika (Tomoyuki Chikanaga) wrote in #note-1:

In my environment, removing exts.mk in build directory resolved the issue.

This worked for me, too.

Updated by hsbt (Hiroshi SHIBATA) 19 days ago Actions #4

  • Target version changed from 4.1 to 4.0

Updated by hsbt (Hiroshi SHIBATA) 19 days ago Actions #5

  • Target version deleted (4.0)
Actions

Also available in: PDF Atom