2011-06-14 6 views
1

이유가 무엇인지 알 수 없습니다. 다음 단계를 설명하고 싶습니다.RVM 설치 문제

Ubuntu:~$ which ruby 
/usr/local/bin/ruby 
$ bash < <(curl https://rvm.beginrescueend.com/releases/rvm-install-head) 

.bashrc 파일을 변경했습니다. 여기에 내가 RVM 노트를 수행 할 때, 그것은 "발견되지 명령 'RVM은'하지만 RVM (20)과 비슷한 사람이 있습니다 : 명령을 찾을 수 없습니다"가 말한다 지금 내 파일

# ~/.bashrc: executed by bash(1) for non-login shells. 
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc) 
# for examples 

# If not running interactively, don't do anything 
if [[ -n "$PS1" ]]; then 

# don't put duplicate lines in the history. See bash(1) for more options 
# ... or force ignoredups and ignorespace 
HISTCONTROL=ignoredups:ignorespace 

# append to the history file, don't overwrite it 
shopt -s histappend 

# for setting history length see HISTSIZE and HISTFILESIZE in bash(1) 
HISTSIZE=1000 
HISTFILESIZE=2000 

# check the window size after each command and, if necessary, 
# update the values of LINES and COLUMNS. 
shopt -s checkwinsize 

# make less more friendly for non-text input files, see lesspipe(1) 
[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)" 

# set variable identifying the chroot you work in (used in the prompt below) 
if [ -z "$debian_chroot" ] && [ -r /etc/debian_chroot ]; then 
    debian_chroot=$(cat /etc/debian_chroot) 
fi 

# set a fancy prompt (non-color, unless we know we "want" color) 
case "$TERM" in 
    xterm-color) color_prompt=yes;; 
esac 

# uncomment for a colored prompt, if the terminal has the capability; turned 
# off by default to not distract the user: the focus in a terminal window 
# should be on the output of commands, not on the prompt 
#force_color_prompt=yes 

if [ -n "$force_color_prompt" ]; then 
    if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then 
    # We have color support; assume it's compliant with Ecma-48 
    # (ISO/IEC-6429). (Lack of such support is extremely rare, and such 
    # a case would tend to support setf rather than setaf.) 
    color_prompt=yes 
    else 
    color_prompt= 
    fi 
fi 

if [ "$color_prompt" = yes ]; then 
    PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\[email protected]\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ ' 
else 
    PS1='${debian_chroot:+($debian_chroot)}\[email protected]\h:\w\$ ' 
fi 
unset color_prompt force_color_prompt 

# If this is an xterm set the title to [email protected]:dir 
case "$TERM" in 
xterm*|rxvt*) 
    PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\[email protected]\h: \w\a\]$PS1" 
    ;; 
*) 
    ;; 
esac 

# enable color support of ls and also add handy aliases 
if [ -x /usr/bin/dircolors ]; then 
    test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)" 
    alias ls='ls --color=auto' 
    #alias dir='dir --color=auto' 
    #alias vdir='vdir --color=auto' 

    alias grep='grep --color=auto' 
    alias fgrep='fgrep --color=auto' 
    alias egrep='egrep --color=auto' 
fi 

# some more ls aliases 
alias ll='ls -alF' 
alias la='ls -A' 
alias l='ls -CF' 

# Add an "alert" alias for long running commands. Use like so: 
# sleep 10; alert 
alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]\s*alert$//'\'')"' 

# Alias definitions. 
# You may want to put all your additions into a separate file like 
# ~/.bash_aliases, instead of adding them here directly. 
# See /usr/share/doc/bash-doc/examples in the bash-doc package. 

if [ -f ~/.bash_aliases ]; then 
    . ~/.bash_aliases 
fi 

# enable programmable completion features (you don't need to enable 
# this, if it's already enabled in /etc/bash.bashrc and /etc/profile 
# sources /etc/bash.bashrc). 
if [ -f /etc/bash_completion ] && ! shopt -oq posix; then 
    . /etc/bash_completion 
fi 

if [[ -s $HOME/.rvm/scripts/rvm ]] ; then source $HOME/.rvm/scripts/rvm ; fi 

fi 

입니다

위치를 알아낼 수 없습니다 나는 잘못했다.

+4

.bashrc를 다시 보내셨습니까? 예 : '. .bashrc '또는'source .bashrc'. – Brian

+0

@Brian .... nop..thanx 바보 같은 실수를 수정했습니다 – Bijendra

+0

rvm은 비대화 형 쉘에서도 사용할 수 있어야하므로 최종 fi 아래에서 rvm을 소싱해야합니다. – YonahW

답변

0

~/.bashrc 파일의 어딘가에 문제가있는 것 같습니다. 당신은 당신이 그것을 편집 후 소스 확인 할 수 있습니다 : 당신이 다른 문제가있는 경우 http://blog.dcxn.com/2011/06/20/setting-up-rvm-on-ubuntu-11-04/

그것을 체크 아웃 : 나는 RVM 우분투 11.04에 완벽하게 작동하기에 대한 짧은 자습서를 작성했습니다

source ~/.bashrc 

. 매우 일반적인 문제는 의존성이 설치되어 있지 않다는 것입니다.