From: duerst Date: 2022-03-29T01:19:47+00:00 Subject: [ruby-core:108101] [Ruby master Bug#18666] No rule to make target 'yaml/yaml.h', needed by 'api.o' Issue #18666 has been updated by duerst (Martin D��rst). File mkmf.log added I created and successfully compiled a completely new clone of Ruby. That had no problem finding the `yaml.h` file. The corresponding `mkmf.log` file from `ext/psych` is attached. The conclusion seems to be that when bundled sources were removed, there was no mechanism to trigger the right steps to fix whatever needed to be fixing in the Makefile or thereabouts. I hope this can be fixed in future cases where bundled sources are removed. ---------------------------------------- Bug #18666: No rule to make target 'yaml/yaml.h', needed by 'api.o' https://bugs.ruby-lang.org/issues/18666#change-97065 * Author: duerst (Martin D��rst) * Status: Open * Priority: Normal * Assignee: hsbt (Hiroshi SHIBATA) * ruby -v: ruby 3.1.0dev (2021-06-03T06:59:33Z master 7e14762159) [x86_64-linux] * Backport: 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN ---------------------------------------- When updating my Ruby compilation with `make up; make`, I hit the following error: ``` make[2]: Entering directory '/home/duerst/14ruby/ext/psych' make[2]: *** No rule to make target 'yaml/yaml.h', needed by 'api.o'. Stop. make[2]: Leaving directory '/home/duerst/14ruby/ext/psych' make[1]: *** [exts.mk:262: ext/psych/all] Error 2 make[1]: Leaving directory '/home/duerst/14ruby' make: *** [uncommon.mk:307: build-ext] Error 2 ``` `./ruby -v` is `ruby 3.2.0dev (2022-03-22T19:51:05Z master 0140e6c41e) [x86_64-linux]` All of this is on Ubuntu 20.04 on WSL2 on Windows 10. My guess is that this bug is related to recent changes in psych/yaml/... ---Files-------------------------------- mkmf.log (14.8 KB) mkmf.log (2.57 KB) -- https://bugs.ruby-lang.org/ Unsubscribe: