Issue #7819 has been updated by nobu (Nobuyoshi Nakada).

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.
----------------------------------------
Bug #7819: configure script doesn't recognize valid options
https://bugs.ruby-lang.org/issues/7819#change-36121

Author: telemachus (Peter Aronoff)
Status: Closed
Priority: Normal
Assignee: 
Category: build
Target version: 1.9.3
ruby -v: ruby 1.9.3p385 (2013-02-06 revision 39114) [x86_64-darwin12.2.0]


When configuring the latest version of Ruby, the configure script issues warnings about "unrecognized" but valid (?) build options.

To reproduce:

1. Untar the 1.9.3-p385.tar.gz
2. Give the following options to the configure script:

    ./configure --prefix=/usr/local/ruby-1.9.3-p385 \
            --with-openssl-dir=/usr/local \
            --with-readline-dir=/usr/local \
            --with-yaml-dir=/usr/local \
            --with-gdbm-dir=/usr/local \
            --with-libffi-dir=/usr/local

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. 


-- 
http://bugs.ruby-lang.org/