Spaces in drive name cause the build to fail

[manuchap]

I have two drives:
One ssd with the system called "Mountain Lion".
One hybrid with my home called "Macintosh HD" (previously Snow Leopard disk).

I noticed in my log that the first command invoked by rbenv install 1.9.3-p448 was:

This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by yaml configure 0.1.4, which was
generated by GNU Autoconf 2.67.  Invocation command line was

  $ ./configure --prefix=/Volumes/Macintosh HD/manuchap/.rbenv/versions/1.9.3-p448

which led to a build fail due to:

configure:3243: checking whether the C compiler works
configure:3265: gcc  -I'/Volumes/Macintosh HD/manuchap/.rbenv/versions/1.9.3-p448/include'  -L'/Volumes/Macintosh HD/manuchap/.rbenv/versions/1.9.3-p448/lib'  conftest.c  >&5
i686-apple-darwin11-llvm-gcc-4.2: HD/manuchap/.rbenv/versions/1.9.3-p448/include': No such file or directory
i686-apple-darwin11-llvm-gcc-4.2: HD/manuchap/.rbenv/versions/1.9.3-p448/lib': No such file or directory

So I mapped my drives as such:

$/Volumes: ln -s "Mountain Lion" lion
$/Volumes: ln -s "Macintosh HD" data

and tried:

$~/: CONFIGURE_OPTS=" --prefix=/Volumes/data/manuchap/.rbenv/versions/1.9.3-p448"

which led to:

This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by yaml configure 0.1.4, which was
generated by GNU Autoconf 2.67.  Invocation command line was

  $ ./configure --prefix=/Volumes/Macintosh HD/manuchap/.rbenv/versions/1.9.3-p448 --prefix=/Volumes/data/manuchap/.rbenv/versions/1.9.3-p448

full log
It seems the options are declared twice.
Can I just run _./configure CONFIGURE_OPTS="--prefix=/Volumes/data/manuchap/.rbenv/versions/1.9.3-p448" && make && make install_ in the failed build folder (/var/folders/88/rbsr__h56tx85bgmgw70lyq40000gn/T/ruby-build.20130717055252.7678/yaml-0.1.4/) or is there a workaround this?
Thanks!

[manuchap]

Issue solved!
Hopefully my home was on another drive so I renamed the drive and pointed my home on it from a guest account and voilà!