Baseruby is required after patching configure.in
It sometimes happens, that during packaging Ruby, it is necessary to patch configure.in (we are doing so in Fedora, there are patches in Debian, RVM does so occasionally as well). Unfortunately, since rev 42685, if the configure.in is patched, it has newer timestamp than sizes.c and therefore sizes.c should be regenerated. For that Ruby is required. Unfortunately, miniruby is not build yet at that stage and we don't want to have other Ruby on the system, due to possible bootstrapping issues.
I can workaround it by
touch sizes.c after the patch is applied, but is there change to remove/fix this dependency? Thanks.
common.mk: make sizes.c with MINIRUBY
- common.mk (sizes.c): use MINIRUBY because Init_sizes() for miniruby is defined in miniinit.c and miniruby does not depend on this file. [Bug #8968]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@43137 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
common.mk: sizes.c depends on PREP now
- common.mk (sizes.c): now depends on PREP, which is miniruby if native compile or fake.rb otherwise, to run MINIRUBY [Bug #8968]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@43145 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
Updated by vo.x (Vit Ondruch) about 6 years ago
nobu (Nobuyoshi Nakada) wrote:
Not only sizes.c, you need BASERUBY to generate some source files after touching template files.
It's your responsibility.
Yes, it may happen that I may need to change some template for whatever reason, but configure.in is probably one of the first files which needs to be changed for whatever reason. For example similar patch like this one  is applied to Fedora's package for ages. Not sure if that makes sense to propose it upstream.