Bug #16905
openRuby required to build Ruby on Haiku?
Description
Building Ruby on Haiku results in the following error:
executable host ruby is required. use --with-baseruby option.
Build environment:
~> uname -a
Haiku shredder 1 hrev54197 May 14 2020 06:44:52 x86_64 x86_64 Haiku
Current recipe and patch set:
https://github.com/extrowerk/haikuports/tree/ruby_2.7.1/dev-lang/ruby
Files
Updated by extrowerk (Zoltán Mizsei) over 4 years ago
make distclean doesn't solved the problem.
Updated by shevegen (Robert A. Heiler) over 4 years ago
This could perhaps be a bug. I think you can normally build "miniruby"
if a base ruby is not available on the computer system, and then the
compilation step uses that miniruby for the compilation part. At the
least this is how I understood it to work.
Hopefully someone from the core team can have a look - would be great
if ruby could work on HaikuOS out of the box.
Updated by extrowerk (Zoltán Mizsei) over 4 years ago
shevegen (Robert A. Heiler) wrote in #note-2:
This could perhaps be a bug. I think you can normally build "miniruby"
if a base ruby is not available on the computer system, and then the
compilation step uses that miniruby for the compilation part. At the
least this is how I understood it to work.
Forgot to mention i maintain the ruby port since some years, so i am definitely sure the earlier versions never had problem like this.
Hopefully someone from the core team can have a look - would be great
if ruby could work on HaikuOS out of the box.
2.7.0p0 is the current running version on Haiku. I will look deeper into it later to find the culprit.
Updated by nobu (Nobuyoshi Nakada) over 4 years ago
According to the log,
executable host ruby is required. use --with-baseruby option.
uncommon.mk:866: recipe for target 'parse.c' failed
make: *** [parse.c] Error 1
parse.y file has been modified, or its timestamp changed at least.
Updated by extrowerk (Zoltán Mizsei) over 4 years ago
parse.y file has been modified, or its timestamp changed at least.
I didn't edited that file and haven't changed the timestamp, so while your idea makes sense, i don't trust this error message at all, as this is from make, not from flex/bison, so it is way too generic error to be able to tell whats going on here. Let's see what is in the debug output...