Bug #6508


Add an (optional) GNU configure option to demand libyaml before continuing, when compiling ruby from source

Added by shevegen (Robert A. Heiler) over 10 years ago. Updated about 10 years ago.

Target version:
ruby -v:
ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-linux]


Hi. When I compile ruby 1.9.3 I get this sometimes:

It seems your ruby installation is missing psych (for YAML output).
To eliminate this warning, please install libyaml and reinstall your ruby.

This is a bit annoying because I need yaml support, so I have to
recompile anyway. So I first compile libyaml, then I recompile ruby.

I had a look at ./configure --help but there was no option provided
to require libyaml before continuing.

My suggestion is to add this to the configure script, so that users
like me can know that the ruby that was compiled 100% has libyaml
support or 100% does not have libyaml support.

Option for configure:

--with-libyaml Require a working libyaml installation before continuing.

If libyaml is not installed at configure-time, the configure script
stops with this message (suggestion):

"We were unable to find a working libyaml installation. As --with-libyaml
was passed, we can not continue before you have installed libyaml. Please
install libyaml, either from source such as from
or from your distribution's package manager."

Thanks for reading and considering! I like ruby but the change to
yaml is a bit annoying when compiling ruby, for me it is much easier
if the configure script does not continue, if it has such an option.

Updated by shyouhei (Shyouhei Urabe) over 10 years ago

@shevegen (Robert A. Heiler) have you tried adding --with-libyaml to your configure args? We already have it (with a different context).

Generary speaking what @shevegen (Robert A. Heiler) needs is a way to mandate build process to compile a specific extension lib. I know the motivation.

Updated by mame (Yusuke Endoh) over 10 years ago

  • Status changed from Open to Feedback

I completely agree that the behavior you are proposing is best.
But it would be hard to implement exactly because the library (libyaml) is searched by extconf.rb, which requires ruby executable (miniruby).
So, it is impossible to make configure fail when there is no libyaml.

To be exact, it is possible if not only extconf.rb but also configure checks libyaml.
But it would be also hard to accept this method, in terms of maintenance.

Please let us know if you have any alternative implementation approach.
If there is no proposal, I'm sorry but I'll reject this ticket.

Yusuke Endoh

Updated by mame (Yusuke Endoh) about 10 years ago

  • Status changed from Feedback to Rejected

Also available in: Atom PDF