From: "hsbt (Hiroshi SHIBATA) via ruby-core" Date: 2025-01-28T01:51:36+00:00 Subject: [ruby-core:120805] [Ruby master Bug#21092] error building ruby 3.4.1 on cygwin Issue #21092 has been updated by hsbt (Hiroshi SHIBATA). Status changed from Open to Assigned Assignee set to hsbt (Hiroshi SHIBATA) I could reproduce this. https://github.com/ruby/ruby/actions/runs/13001828367/job/36261824250?pr=12649 ---------------------------------------- Bug #21092: error building ruby 3.4.1 on cygwin https://bugs.ruby-lang.org/issues/21092#change-111672 * Author: jeremyd2019 (Jeremy Drake) * Status: Assigned * Assignee: hsbt (Hiroshi SHIBATA) * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- While building from the release tarball ruby-3.4.1.tar.xz on cygwin (also confirmed in snapshot-master.tar.gz from Jan 27, 2025), I get the following error: ../ruby-3.4.1/ext/extmk.rb:279:in 'Array#-': no implicit conversion of nil into Array (TypeError) from ../ruby-3.4.1/ext/extmk.rb:279:in 'Object#extmake' from ../ruby-3.4.1/ext/extmk.rb:659:in 'block in
' from ../ruby-3.4.1/ext/extmk.rb:653:in 'Array#each' from ../ruby-3.4.1/ext/extmk.rb:653:in '
' I have tracked this down to happening when an ext writes a dummy makefile. In this case, that ext is .bundle/gems/syslog-0.2.0. See https://github.com/ruby/syslog/pull/16 for fixing why it is writing a dummy makefile to begin with, but still, it seems like extmk.rb should handle this case gracefully rather than breaking the build. -- https://bugs.ruby-lang.org/ ______________________________________________ ruby-core mailing list -- ruby-core@ml.ruby-lang.org To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/