RVM Warning! PATH is not properly set up
I have the same problem with rvm 1.25.26.
solution:
I've modified ~/.bashrc
as follows:
## rvmPATH="$GEM_HOME/bin:$HOME/.rvm/bin:$PATH" # Add RVM to PATH for scripting[ -s ${HOME}/.rvm/scripts/rvm ] && source ${HOME}/.rvm/scripts/rvm
causing:
Warning is fired at __rvm_path_match_gem_home_check() function in $HOME/.rvm/scripts/functions/cli
.
If the beginning of $PATH
does not start from $GEM_HOME/bin
, a warning message is displayed.
__rvm_path_match_gem_home_check(){ (( ${rvm_silence_path_mismatch_check_flag:-0} == 0 )) || return 0 [[ -n "${GEM_HOME:-}" ]] || return 0 case "$PATH:" in ($GEM_HOME/bin:*) true ;; # all fine here (*:$GEM_HOME/bin:*) __rvm_path_match_gem_home_check_warning "is not at first place" ;; (*) __rvm_path_match_gem_home_check_warning "is not available" ;; esac}
In my case, Heroku had added the following to my .bashrc:
### Added by the Heroku Toolbeltexport PATH="/usr/local/heroku/bin:$PATH"
Notice how it's prepending itself to the path. All I had to do was switch it around to:
### Added by the Heroku Toolbeltexport PATH="$PATH:/usr/local/heroku/bin"
And my problem was solved!
If you don't have Heroku, look for anything else that may be prepending itself to your path. Really, RVM just wants to make sure it has a fair chance to load Ruby before any gems that include themselves in the path get loaded.