You have to keep in mind that each time you run

export ROS_PACKAGE_PATH=/my/package/path

you are overwriting the previous value of that variable. That's why it cannot find where the base ROS packages are. In any case, the path I told you before was not correct, I think it should work if you remove the line that says 

export ROS_PACKAGE_PATH=/home/mars/ros/stacks 

and substitute the line that says

export ROS_PACKAGE_PATH=/home/mars/ros/omnibot

with

export ROS_PACKAGE_PATH=/home/mars/ros/omnibot:$ROS_PACKAGE_PATH

That way you are prepending your package path to the previous content of ROS_PACKAGE_PATH instead of substituting it.

Miguel.

El 16/07/2010, a las 19:06, ibwood escribió:

> 
> It might help to look at my bash file (.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
> [ -z "$PS1" ] && return
> 
> # don't put duplicate lines in the history. See bash(1) for more options
> # don't overwrite GNU Midnight Commander's setting of `ignorespace'.
> HISTCONTROL=$HISTCONTROL${HISTCONTROL+,}ignoredups
> # ... or force ignoredups and ignorespace
> 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)
> 
> # 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\]\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 -l'
> #alias la='ls -A'
> #alias l='ls -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
> 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
> source /opt/ros/boxturtle/setup.sh
> source ~/ros-tutorials/setup.sh
> export EDITOR='emacs -nw'
> 
> export ROS_ROOT=~/ros
> export ROS_PACKAGE_PATH=/home/mars/ros/omnibot
> export ROS_PACKAGE_PATH=/home/mars/ros/stacks
> export ROS_IP=192.168.1.108
> export ROS_MASTER_URI=http://192.168.1.108:11311/
> export PATH=$ROS_ROOT/bin:$PATH
> export PYTHONPATH=$ROS_ROOT/core/roslib/src:$PYTHONPATH
> export OCTAVE_PATH=$ROS_ROOT/core/experimental/rosoct/octave:$OCTAVE_PATH
> source $ROS_ROOT/tools/rosbash/rosbash
> -- 
> View this message in context: http://ros-users.122217.n3.nabble.com/Dependencies-of-a-stack-tp972858p973033.html
> Sent from the ROS-Users mailing list archive at Nabble.com.
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> ros-users mailing list
> ros-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ros-users
> _______________________________________________
> ros-users mailing list
> ros-users@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users