Some computer system administrators have placed "common" libraries and
header files in non-standard locations which complicates building ruby.
 It can be done with a very long ./configure command, but their level
of apathy usually means they get it wrong.  For example, the readline
package is in some utils directory that must be mentioned on the
../configure command line.

Is there a simple ruby script that could be run (using the newly built
ruby) that would report what was successfully built and what was
omitted, etc. (and maybe what dependency was missing)?  They could then
hunt down their carefully hidden libraries and header files, etc., to
build a "complete" ruby.

Thanks!