Compile the source 5.0 / 6.0 on the machine, installed jdk1.7, then due to the need to compile 4.2.2, it is also a jdk1.6 install, configure the environment variables
gedit / etc / environment into the following
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games"
PATH="$PATH:/usr/lib/jvm/jdk1.6.0_43/bin:/usr/lib/jvm/jdk1.6.0_43"
JAVAHOME="/usr/lib/jvm/jdk1.6.0_43"
CLASSPATH="$JAVAHOME/lib:$JAVAHOME/jre/lib"
JRE_HOME=$JAVA_HOME/jre
After compiling the source code successfully, restart the next day and found the graphical login screen login password is not correct, the cycle jumps back to the login screen.
Ctrl + Alt + F1 to enter tty1, enter your user name and password, but the basic commands are impossible, such as reboot / ls / rm / nano / vi will not work, suggesting
The command could not be located because '/usr/bin:/bin' is not included in the PATH environment variable.
Later in the online search to http://blog.163.com/shao_yuru/blog/static/130517606201010310581842/
Deleted / etc section / environment to add, remember to back up before the amendment, restart normally.
The reason is the nature of / etc / environment PATH command path system is the first, the second and then assigned to cover the PATH system can not find the cause command.
http://www.oschina.net/question/1762880_233348 is the same problem
gedit ~ / .bashrc in the modified source ~ / .bashrc into force
The following is my personal opinion, in general, in Linux, I do not like to modify / etc / profile in the content, there is equivalent to the system environment variables, we only need to change their general use
User environment variable configuration file (.bashrc) you can, so you can ensure the independence of multiple users. Of course, for Eclipse (or for Java) this tool, if you think the
Users should use, modify / etc / profile may have merit.
However, if you are like me and would eclipse jdk are placed in their own home directory, modify the .bashrc is quite justified, because .bashrc is their own thing.
gedit ~ / .bashrc configured as follows
#add for jdk1.6
export JAVAHOME="/usr/lib/jvm/jdk1.6.0_43"
export JRE_HOME=${JAVA_HOME}/jre
export CLASSPATH=.:${JAVA_HOME}/lib:${JRE_HOME}/lib
export PATH=${JAVA_HOME}/bin:$PATH
export PATH=${PATH}:/root/Tools/sdk/tools
export PATH=${PATH}:/root/Tools/sdk/platform-tools
#add for 4418 gcc
export PATH=/opt/FriendlyARM/toolchain/4.9.3/bin:$PATH
export GCC_COLORS=auto
#add of NDK
export NDK=/opt/ndk/android-ndk-r10c
export PATH=$NDK:$PATH
# ~/.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
[ -z "$PS1" ] && return
# 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)
be
# 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=
be
be
if [ "$color_prompt" = yes ]; then
PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
else
PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
be
unset color_prompt force_color_prompt
# If this is an xterm set the title to user@host:dir
case "$TERM" in
xterm*|rxvt*)
PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\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 flag = auto'
#alias vdir='vdir --color=auto'
alias grep = 'grep --color = auto'
alias fgrep='fgrep --color=auto'
alias egrep='egrep --color=auto'
be
# some more ls aliases
alias ll='ls -alF'
alias = 'ls -A'
other L 'is -cf'
# 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
be
# 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
#be
Author: Mizuki well
link: https: //www.jianshu.com/p/44ec005546fe
Source: Jane books
are copyrighted by the author. Commercial reprint please contact the author authorized, non-commercial reprint please indicate the source.