Bad GEM_PATH on fresh Win7 install

Ruby JRuby
#1

I just did an install of JRuby 1.6.1 on a fresh install of Win7x64. This
Windows environment is running under VMWare.

After the installation, I am unable to install any gems. I get an ENOENT
error:

I googled for this issue and ran across a few responses on stackoverflow
about modifying the gem.bat file. However, that change did not help.

Additionally, when I look at my ‘gem env’ it prints one of the network
drives even though I disconnected it prior to starting the install.

Any ideas on how I can fix this?

cr

#2

On May 5, 2011, at 2:33 PM, Chuck R. wrote:

https://gist.github.com/957717

Any ideas on how I can fix this?

The fix was to create a %HOME% variable pointing to c:\Users\cremes. For
some reason, the install4j installer picked up \vmware-host\Shared
Folders as the user.home (according to the installation.log). By adding
that environment variable, it must have short-circuited whatever logic
is used by the installer for determining the home directory. That logic
apparently has a flaw.

I would like to open a JIRA on this but I don’t have instructions for an
easily reproducible case. Any suggestions?

cr

#3

On Thu, May 5, 2011 at 3:30 PM, Chuck R. [email protected]
wrote:

Additionally, when I look at my ‘gem env’ it prints one of the network drives
even though I disconnected it prior to starting the install.

https://gist.github.com/957717

Any ideas on how I can fix this?

The fix was to create a %HOME% variable pointing to c:\Users\cremes. For some
reason, the install4j installer picked up \vmware-host\Shared Folders as the
user.home (according to the installation.log). By adding that environment
variable, it must have short-circuited whatever logic is used by the installer for
determining the home directory. That logic apparently has a flaw.

I would like to open a JIRA on this but I don’t have instructions for an easily
reproducible case. Any suggestions?

Just do due diligence to describe it as best you can. Perhaps we will
think of a nice reproduction later, but it doesn’t hurt to report what
you have.

-Tom

–
blog: http://blog.enebo.com twitter: tom_enebo
mail: [email protected]