Issue #22003 has been updated by nagachika (Tomoyuki Chikanaga). Backport changed from 3.3: DONTNEED, 3.4: REQUIRED, 4.0: DONE to 3.3: DONTNEED, 3.4: DONE, 4.0: DONE ruby_3_4 commit:335d51fb77c66e75f9efcb790c28dee437129f5c merged revision(s) commit:e52562edc0c26a905bec575215f6ac4e7fcdd59f. ---------------------------------------- Bug #22003: .bundle extensions not built when doing out-of-source build https://bugs.ruby-lang.org/issues/22003#change-117639 * Author: Kulikjak (Jakub Kulik) * Status: Closed * ruby -v: ruby 4.0.2 (2026-03-17 revision d3da9fec82) +PRISM [amd64-solaris2.11] * Backport: 3.3: DONTNEED, 3.4: DONE, 4.0: DONE ---------------------------------------- Hi, I encountered a pretty edge case extension build bug. When building Ruby out-of-source and executing the configure script with a full path in a workspace that contains "test" in its name, it fails to build all the extensions in the `.bundle/gems` directory. It can be easily reporoduced with the following: ```
pwd /builds/testing/components/ruby/ruby-40 mkdir build cd build /builds/testing/components/ruby/ruby-40/ruby-4.0.2/configure ... /usr/gnu/bin/make -j 20 ... <the stuff in the .bundle directory is not built>
When doing it this way, the `srcdir` variable in the Makefile will be an absolute path, which is then used in `ext/configure-ext.mk` target and in `configure-ext.mk.tmpl` `Dir.glob` call, where the following line:
% next if extconf.any?{|f| f.include?(".bundle/gems") && f.include?("test") } ``` makes it omit all the extensions in the ".bundle/gems" directory. The problem is not there when I use a relative path (`../ruby-4.0.2/configure`) or when building directly in `ruby-4.0.2` (because the `srcdir` is relative in those cases). -- https://bugs.ruby-lang.org/