configure script doesn't recognize valid options
When configuring the latest version of Ruby, the configure script issues warnings about "unrecognized" but valid (?) build options.
Untar the 1.9.3-p385.tar.gz
Give the following options to the configure script:
The result is this warning, both at the top and the bottom of the configuration output:
configure: WARNING: unrecognized options: --with-openssl-dir, --with-readline-dir, --with-yaml-dir, --with-gdbm-dir, --with-libffi-dir
Based on discussion in irc and the results of the build, I think that the warnings are bogus. That is, those options are recognized and used in the build.
Updated by nobu (Nobuyoshi Nakada) almost 10 years ago
- Subject changed from configure script doesn't recognize valid options to configure script doesn't recognize valid options
- Status changed from Open to Closed
You're right, it's just a warning.
Or, just use only --with-opt-dir=/usr/local instead.
Updated by naruse (Yui NARUSE) almost 10 years ago
Wonbyte (Greg Sieranski) wrote:
So the --with options are correct to use? Even with Ruby-2.0.0-p0?
Yes, it is correct.
Why it shows such warnings is configure itself actually ignores them, but later build process use them.