catkin_make時のエラー ”No module named 'catkin_pkg'”

[akira....@em.ci.ritsumei.ac.jp]

http://wiki.ros.org/ja/ROS/Tutorials/InstallingandConfiguringROSEnvironment

に従ってワークスペースをつくろうとしたのですが,

catkin_makeの時点で以下のようなエラーが起きてしまいます.最近anacondaからPythonをバージョンアップしたのが原因かと思われるのですが,解決方法がわかりません.

Ubuntu14.04 indigo です

 

$ catkin_make
Base path: /home/near/catkin_ws
Source space: /home/near/catkin_ws/src
Build space: /home/near/catkin_ws/build
Devel space: /home/near/catkin_ws/devel
Install space: /home/near/catkin_ws/install
####
#### Running command: "cmake /home/near/catkin_ws/src -DCATKIN_DEVEL_PREFIX=/home/near/catkin_ws/devel -DCMAKE_INSTALL_PREFIX=/home/near/catkin_ws/install -G Unix Makefiles" in "/home/near/catkin_ws/build"
####
-- The C compiler identification is GNU 4.9.4
-- The CXX compiler identification is GNU 4.9.4
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Using CATKIN_DEVEL_PREFIX: /home/near/catkin_ws/devel
-- Using CMAKE_PREFIX_PATH: /opt/ros/indigo
-- This workspace overlays: /opt/ros/indigo
-- Found PythonInterp: /home/near/anaconda3/bin/python (found version "3.5.2") 
-- Using PYTHON_EXECUTABLE: /home/near/anaconda3/bin/python
-- Using Debian Python package layout
-- Using empy: /usr/bin/empy
-- Using CATKIN_ENABLE_TESTING: ON
-- Call enable_testing()
-- Using CATKIN_TEST_RESULTS_DIR: /home/near/catkin_ws/build/test_results
-- Looking for include file pthread.h
-- Looking for include file pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE  
-- Found gtest sources under '/usr/src/gtest': gtests will be built
-- Using Python nosetests: /home/near/anaconda3/bin/nosetests
ImportError: "from catkin_pkg.package import parse_package" failed: No module named 'catkin_pkg'
Make sure that you have installed "catkin_pkg", it is up to date and on the PYTHONPATH.
CMake Error at /opt/ros/indigo/share/catkin/cmake/safe_execute_process.cmake:11 (message):
  execute_process(/home/near/anaconda3/bin/python
  "/opt/ros/indigo/share/catkin/cmake/parse_package_xml.py"
  "/opt/ros/indigo/share/catkin/cmake/../package.xml"
  "/home/near/catkin_ws/build/catkin/catkin_generated/version/package.cmake")
  returned error code 1
Call Stack (most recent call first):
  /opt/ros/indigo/share/catkin/cmake/catkin_package_xml.cmake:63 (safe_execute_process)
  /opt/ros/indigo/share/catkin/cmake/all.cmake:151 (_catkin_package_xml)
  /opt/ros/indigo/share/catkin/cmake/catkinConfig.cmake:20 (include)
  CMakeLists.txt:52 (find_package)

-- Configuring incomplete, errors occurred!
See also "/home/near/catkin_ws/build/CMakeFiles/CMakeOutput.log".
See also "/home/near/catkin_ws/build/CMakeFiles/CMakeError.log".
Invoking "cmake" failed

Pythonのバージョンは以下になります

$ python -V
Python 3.5.2 :: Anaconda 4.2.0 (64-bit)

pythonpathは以下になります 

$ env | grep python
PYTHONPATH=/opt/ros/indigo/lib/python2.7/dist-packages

[akira....@em.ci.ritsumei.ac.jp]

.bashrcは以下になります

$ cat ~/.bashrc
# ~/.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
case $- in
    *i*) ;;
      *) return;;
esac
# don't put duplicate lines or lines starting with space in the history.
# See bash(1) for more options
HISTCONTROL=ignoreboth
# 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
# If set, the pattern "**" used in a pathname expansion context will
# match all files and zero or more directories and subdirectories.
#shopt -s globstar
# 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\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
else
    PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
fi
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=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 ! shopt -oq posix; then
  if [ -f /usr/share/bash-completion/bash_completion ]; then
    . /usr/share/bash-completion/bash_completion
  elif [ -f /etc/bash_completion ]; then
    . /etc/bash_completion
  fi
fi
#!/bin/sh java -jar /home/near/.bin/josm-tested.jar
# please set network-interface
network_if=eth0

# added by Anaconda3 4.2.0 installer
 export PATH="/home/near/anaconda3/bin:$PATH"
source /opt/ros/indigo/setup.bash

 

[Moirai]

基本的にROSはUbuntuの標準システムをベースにシステムが作られていますので，Ubuntu標準のPythonを使うことを**強く**おすすめします．

anacondaをdisableしてください．

その後、一度

   rm -fr ~/catkin_ws/devel ~/catkin_ws/build

としてワークスペースを綺麗にするのが良いかと思います．

（参考：http://answers.ros.org/question/220546/catkin_make-failure-due-to-python-anaconda/ ）

それ以外の解法としては pip install catkin-pkg すれば現状の問題は解決できると思いますが，この先もAnaconda絡みの更なる問題が現れると思います．

Anacondaを生かしたままにしたいのだとすると，結局は本格的にROS/Anaconda のプロジェクトを始めることになるかと思います．

（新しいプロジェクトは大歓迎されますので是非！）

[akira....@em.ci.ritsumei.ac.jp]

Anacondaをアンインストールし,標準のPythonを利用したところ,上手くmakeが通りました.

 sudo rm -rf /anaconda をした後,.bashrcに記述されているAnacondaのパス設定を消去しました.

回答ありがとうございます.

2016年11月17日木曜日 1時13分29秒 UTC+9 Moirai:

基本的にROSはUbuntuの標準システムをベースにシステムが作られていますので，Ubuntu標準のPythonを使うことを**強く**おすすめします．

anacondaをdisableしてください．

その後、一度

   rm -fr ~/catkin_ws/devel ~/catkin_ws/builda