orocos_toolchain_ros/orogen

Hello Orocos,

I am having an issue in starting using the "orocos_toolchain_ros" on ROS
Diamondback.
I can't access orogen / or compil it:
$ rosmake orocos_toolchain_ros
...
[rosmake-1] Starting >>> orogen [ make ]
[rosmake-1] Finished <<< orogen ROS_NOBUILD in package orogen
...
there is ROS_NOBUILD files in all subdirectory... so I guess it's because I
use the Debian packaged version .. but then:
$ rosrun orogen orogen
[rosrun] Couldn't find executable named orogen below
/opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
[rosrun] Found the following, but they're either not files,
[rosrun] or not executable:
[rosrun] /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
and I guess I have what I need to make it working...
$ tail ~/.bashrc
# ROS
source /opt/ros/diamondback/setup.bash
# Orocos ROS
source /opt/ros/diamondback/stacks/orocos_toolchain_ros/env.sh
$ orogen
No command 'orogen' found, ...

I am quite new to the all thing so maybe my problem is obvious, and I missd
something...
for the ROS part I think I'm OK (
http://www.ros.org/wiki/diamondback/Installation/Ubuntu )
then for Orocos I followed http://www.ros.org/wiki/orocos_toolchain_ros
sudo apt-get install ros-diamondback-orocos-toolchain-ros

did I miss something ?

Cheers,
Pierrick

orocos_toolchain_ros/orogen

On Fri, Mar 4, 2011 at 4:26 AM, Pierrick Koch <pierrick [dot] koch [..] ...> wrote:
> Hello Orocos,
> I am having an issue in starting using the "orocos_toolchain_ros" on ROS
> Diamondback.
> I can't access orogen / or compil it:
> $ rosmake orocos_toolchain_ros
> ...
> [rosmake-1] Starting >>> orogen [ make ]
> [rosmake-1] Finished <<< orogen ROS_NOBUILD in package orogen
> ...
> there is ROS_NOBUILD files in all subdirectory... so I guess it's because I
> use the Debian packaged version .. but then:
> $ rosrun orogen orogen
> [rosrun] Couldn't find executable named orogen below
> /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
> [rosrun] Found the following, but they're either not files,
> [rosrun] or not executable:
> [rosrun]   /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen

You can't use rosrun to run orogen. First of all, orogen relies on a set of
ruby gems which are not in the 'global path', so this needs to be set with
the GEM_HOME and RUBYLIB directory. The orocos_toolchain_ros/env.sh
file does that, and adds orogen to your PATH.

Peter

PS to others: couldn't we plant a 'dummy' orogen executable which is found
by rosrun and which tells the user to source env.sh ? A next step could be that
this file sources env.sh itself and then calls real orogen.
--
Orocos-Users mailing list
Orocos-Users [..] ...
http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users

Ruben Smits's picture

orocos_toolchain_ros/orogen

On Friday 04 March 2011 09:51:52 Peter Soetens wrote:
> On Fri, Mar 4, 2011 at 4:26 AM, Pierrick Koch <pierrick [dot] koch [..] ...>
wrote:
> > Hello Orocos,
> > I am having an issue in starting using the "orocos_toolchain_ros" on ROS
> > Diamondback.
> > I can't access orogen / or compil it:
> > $ rosmake orocos_toolchain_ros
> > ...
> > [rosmake-1] Starting >>> orogen [ make ]
> > [rosmake-1] Finished <<< orogen ROS_NOBUILD in package orogen
> > ...
> > there is ROS_NOBUILD files in all subdirectory... so I guess it's
> > because I use the Debian packaged version .. but then:
> > $ rosrun orogen orogen
> > [rosrun] Couldn't find executable named orogen below
> > /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
> > [rosrun] Found the following, but they're either not files,
> > [rosrun] or not executable:
> > [rosrun] /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
>
> You can't use rosrun to run orogen. First of all, orogen relies on a set of
> ruby gems which are not in the 'global path', so this needs to be set with
> the GEM_HOME and RUBYLIB directory. The orocos_toolchain_ros/env.sh
> file does that, and adds orogen to your PATH.
>
> Peter
>
> PS to others: couldn't we plant a 'dummy' orogen executable which is found
> by rosrun and which tells the user to source env.sh ? A next step could be
> that this file sources env.sh itself and then calls real orogen.

Something like the following works for me:

diff --git a/bin/ros_orogen.sh b/bin/ros_orogen.sh
new file mode 100755
index 0000000..8a6ec2a
--- /dev/null
+++ b/bin/ros_orogen.sh
@@ -0,0 +1,3 @@
+#!/bin/bash
+source `rosstack find orocos_toolchain_ros`/env.sh
+orogen $@
\ No newline at end of file
diff --git a/bin/ros_typegen.sh b/bin/ros_typegen.sh
new file mode 100755
index 0000000..8f0a77c
--- /dev/null
+++ b/bin/ros_typegen.sh
@@ -0,0 +1,3 @@
+#!/bin/bash
+source `rosstack find orocos_toolchain_ros`/env.sh
+typegen $@
\ No newline at end of file

-- Ruben

orocos_toolchain_ros/orogen

On Friday 04 March 2011 10:26:12 Ruben Smits wrote:
> On Friday 04 March 2011 09:51:52 Peter Soetens wrote:
> > On Fri, Mar 4, 2011 at 4:26 AM, Pierrick Koch <pierrick [dot] koch [..] ...>
>
> wrote:
> > > Hello Orocos,
> > > I am having an issue in starting using the "orocos_toolchain_ros" on
> > > ROS Diamondback.
> > > I can't access orogen / or compil it:
> > > $ rosmake orocos_toolchain_ros
> > > ...
> > > [rosmake-1] Starting >>> orogen [ make ]
> > > [rosmake-1] Finished <<< orogen ROS_NOBUILD in package orogen
> > > ...
> > > there is ROS_NOBUILD files in all subdirectory... so I guess it's
> > > because I use the Debian packaged version .. but then:
> > > $ rosrun orogen orogen
> > > [rosrun] Couldn't find executable named orogen below
> > > /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
> > > [rosrun] Found the following, but they're either not files,
> > > [rosrun] or not executable:
> > > [rosrun] /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
> >
> > You can't use rosrun to run orogen. First of all, orogen relies on a set
> > of ruby gems which are not in the 'global path', so this needs to be set
> > with the GEM_HOME and RUBYLIB directory. The orocos_toolchain_ros/env.sh
> > file does that, and adds orogen to your PATH.
> >
> > Peter
> >
> > PS to others: couldn't we plant a 'dummy' orogen executable which is
> > found by rosrun and which tells the user to source env.sh ? A next step
> > could be that this file sources env.sh itself and then calls real
> > orogen.
>
> Something like the following works for me:
>
> diff --git a/bin/ros_orogen.sh b/bin/ros_orogen.sh
> new file mode 100755
> index 0000000..8a6ec2a
> --- /dev/null
> +++ b/bin/ros_orogen.sh
> @@ -0,0 +1,3 @@
> +#!/bin/bash
> +source `rosstack find orocos_toolchain_ros`/env.sh
> +orogen $@
> \ No newline at end of file
> diff --git a/bin/ros_typegen.sh b/bin/ros_typegen.sh
> new file mode 100755
> index 0000000..8f0a77c
> --- /dev/null
> +++ b/bin/ros_typegen.sh
> @@ -0,0 +1,3 @@
> +#!/bin/bash
> +source `rosstack find orocos_toolchain_ros`/env.sh
> +typegen $@
> \ No newline at end of file

I would at least drop the '.sh' suffix from these filenames.

On the other hand, I don't understand why this error message was given:

> [rosrun] Couldn't find executable named orogen below
> /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
> [rosrun] Found the following, but they're either not files,
> [rosrun] or not executable:
> [rosrun] /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen

instead of:

$ rosrun orogen orogen
/home/kaltan/src/git/orocos-toolchain/orogen/bin/orogen:3:in `require': no
such file to load -- orogen (LoadError)
from /home/kaltan/src/git/orocos-toolchain/orogen/bin/orogen:3

Which is what happens on my side when env.sh is not sourced.

What are the contents of the
/opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen/bin directory
on your system ??

Peter

orocos_toolchain_ros/orogen

Hi Peter,

there is no bin folder in orogen, and a ROS_NO_BUILD file, that I guess is
here to prevent from (re)build...
btw I'm on Ubuntu 10.04 (lucid) i686.

$ ll /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
total 44
drwxr-xr-x 2 root root 4096 2011-03-03 15:27 ./
drwxr-xr-x 18 root root 4096 2011-03-03 15:27 ../
-rw-r--r-- 1 root root 1418 2011-02-07 19:21 CMakeLists.txt
-rw-r--r-- 1 root root 0 2011-03-02 12:51 gems
-rw-r--r-- 1 root root 584 2011-02-07 19:21 mainpage.dox
-rw-r--r-- 1 root root 586 2011-02-07 19:21 Makefile
-rw-r--r-- 1 root root 481 2011-02-07 19:21 Makefile.git
-rw-r--r-- 1 root root 720 2011-02-07 19:21 manifest.xml
-rw-r--r-- 1 root root 47 2011-02-07 19:21 orogen.md5sum
-rw-r--r-- 1 root root 3286 2011-02-07 19:21 orogen.patch
-rw-r--r-- 1 root root 1031 2011-02-07 19:21 README
-rw-r--r-- 1 root root 39 2011-03-02 13:27 ROS_NOBUILD

the package infos are:

$ apt-cache show ros-diamondback-orocos-toolchain-ros
Package: ros-diamondback-orocos-toolchain-ros
Version: 0.2.1-s1299044547~lucid
Architecture: i386
Maintainer: Ruben Smits - Steven Bellens
Installed-Size: 700884
Depends: ros-diamondback-ros (= 1.4.6-s1298587598~lucid),
ros-diamondback-ros-comm (= 1.4.5-s1299027150~lucid),
ros-diamondback-common-msgs (= 1.4.0-s1299027519~lucid), libc6,
build-essential, cmake, python-yaml, subversion, libboost1.40-all-dev,
libxslt1-dev, gccxml, libxml2-dev, antlr, libantlr-dev, ruby1.8-dev,
libopenssl-ruby1.8, rubygems1.8, libreadline-dev, liblua5.1-0-dev, omniorb4,
omniidl4, omniorb4-nameserver, libomniorb4-1, libomniorb4-dev,
libomnithread3-dev, libomnithread3c2
Priority: optional
Section: unknown
Filename:
pool/main/r/ros-diamondback-orocos-toolchain-ros/ros-diamondback-orocos-toolchain-ros_0.2.1-s1299044547~lucid_i386.deb
Size: 182689542
SHA256: 79127c970eacba9f566cf9d9ff38cba49726d9b7c7f16f8bb157b8ae9f2c6c7f
SHA1: 69e33cb252f3e62e5dc16fe259a52ade69390996
MD5sum: fde1c3b1d4fc6c74b7886fcb7d10448a
Description: orocos_toolchain_ros
This stack contains all software necessary to build systems using both
Orocos and ROS infrastructures. The complete Orocos Toolchain is integrated
in the ROS build system and the rtt_ros_integration package allows easy
communication between Orocos components and ROS nodes.
Wg-Rosdistro: diamondback

Cheers,
Pierrick

On Fri, Mar 4, 2011 at 4:49 PM, Peter Soetens <peter [..] ...>wrote:

> On Friday 04 March 2011 10:26:12 Ruben Smits wrote:
> > On Friday 04 March 2011 09:51:52 Peter Soetens wrote:
> > > On Fri, Mar 4, 2011 at 4:26 AM, Pierrick Koch <pierrick [dot] koch [..] ...
> >
> >
> > wrote:
> > > > Hello Orocos,
> > > > I am having an issue in starting using the "orocos_toolchain_ros" on
> > > > ROS Diamondback.
> > > > I can't access orogen / or compil it:
> > > > $ rosmake orocos_toolchain_ros
> > > > ...
> > > > [rosmake-1] Starting >>> orogen [ make ]
> > > > [rosmake-1] Finished <<< orogen ROS_NOBUILD in package orogen
> > > > ...
> > > > there is ROS_NOBUILD files in all subdirectory... so I guess it's
> > > > because I use the Debian packaged version .. but then:
> > > > $ rosrun orogen orogen
> > > > [rosrun] Couldn't find executable named orogen below
> > > > /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
> > > > [rosrun] Found the following, but they're either not files,
> > > > [rosrun] or not executable:
> > > > [rosrun] /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
> > >
> > > You can't use rosrun to run orogen. First of all, orogen relies on a
> set
> > > of ruby gems which are not in the 'global path', so this needs to be
> set
> > > with the GEM_HOME and RUBYLIB directory. The
> orocos_toolchain_ros/env.sh
> > > file does that, and adds orogen to your PATH.
> > >
> > > Peter
> > >
> > > PS to others: couldn't we plant a 'dummy' orogen executable which is
> > > found by rosrun and which tells the user to source env.sh ? A next step
> > > could be that this file sources env.sh itself and then calls real
> > > orogen.
> >
> > Something like the following works for me:
> >
> > diff --git a/bin/ros_orogen.sh b/bin/ros_orogen.sh
> > new file mode 100755
> > index 0000000..8a6ec2a
> > --- /dev/null
> > +++ b/bin/ros_orogen.sh
> > @@ -0,0 +1,3 @@
> > +#!/bin/bash
> > +source `rosstack find orocos_toolchain_ros`/env.sh
> > +orogen $@
> > \ No newline at end of file
> > diff --git a/bin/ros_typegen.sh b/bin/ros_typegen.sh
> > new file mode 100755
> > index 0000000..8f0a77c
> > --- /dev/null
> > +++ b/bin/ros_typegen.sh
> > @@ -0,0 +1,3 @@
> > +#!/bin/bash
> > +source `rosstack find orocos_toolchain_ros`/env.sh
> > +typegen $@
> > \ No newline at end of file
>
> I would at least drop the '.sh' suffix from these filenames.
>
> On the other hand, I don't understand why this error message was given:
>
> > [rosrun] Couldn't find executable named orogen below
> > /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
> > [rosrun] Found the following, but they're either not files,
> > [rosrun] or not executable:
> > [rosrun] /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
>
> instead of:
>
> $ rosrun orogen orogen
> /home/kaltan/src/git/orocos-toolchain/orogen/bin/orogen:3:in `require': no
> such file to load -- orogen (LoadError)
> from /home/kaltan/src/git/orocos-toolchain/orogen/bin/orogen:3
>
>
> Which is what happens on my side when env.sh is not sourced.
>
> What are the contents of the
> /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen/bin directory
> on your system ??
>
> Peter
>

Ruben Smits's picture

orocos_toolchain_ros/orogen

On Monday 07 March 2011 12:17:02 Pierrick Koch wrote:
> Hi Peter,
>
> there is no bin folder in orogen, and a ROS_NO_BUILD file, that I guess is
> here to prevent from (re)build... btw I'm on Ubuntu 10.04 (lucid) i686.
>
> $ ll /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
> total 44
> drwxr-xr-x 2 root root 4096 2011-03-03 15:27 ./
> drwxr-xr-x 18 root root 4096 2011-03-03 15:27 ../
> -rw-r--r-- 1 root root 1418 2011-02-07 19:21 CMakeLists.txt
> -rw-r--r-- 1 root root 0 2011-03-02 12:51 gems
> -rw-r--r-- 1 root root 584 2011-02-07 19:21 mainpage.dox
> -rw-r--r-- 1 root root 586 2011-02-07 19:21 Makefile
> -rw-r--r-- 1 root root 481 2011-02-07 19:21 Makefile.git
> -rw-r--r-- 1 root root 720 2011-02-07 19:21 manifest.xml
> -rw-r--r-- 1 root root 47 2011-02-07 19:21 orogen.md5sum
> -rw-r--r-- 1 root root 3286 2011-02-07 19:21 orogen.patch
> -rw-r--r-- 1 root root 1031 2011-02-07 19:21 README
> -rw-r--r-- 1 root root 39 2011-03-02 13:27 ROS_NOBUILD
>

The debian package building definitely went wrong, since the package isn't
build at all.

Can you retry with master from git?
http://git.mech.kuleuven.be/robotics/orocos_toolchain_ros.git.

The version on git uses submodules instead of downloading the source like
version 0.2.1. I'm in the middle of releasing 0.3.0 which will not have this
issue and which will be in sync with toolchain 2.3

-- Ruben
>
> the package infos are:
>
> $ apt-cache show ros-diamondback-orocos-toolchain-ros
> Package: ros-diamondback-orocos-toolchain-ros
> Version: 0.2.1-s1299044547~lucid
> Architecture: i386
> Maintainer: Ruben Smits - Steven Bellens
> Installed-Size: 700884
> Depends: ros-diamondback-ros (= 1.4.6-s1298587598~lucid),
> ros-diamondback-ros-comm (= 1.4.5-s1299027150~lucid),
> ros-diamondback-common-msgs (= 1.4.0-s1299027519~lucid), libc6,
> build-essential, cmake, python-yaml, subversion, libboost1.40-all-dev,
> libxslt1-dev, gccxml, libxml2-dev, antlr, libantlr-dev, ruby1.8-dev,
> libopenssl-ruby1.8, rubygems1.8, libreadline-dev, liblua5.1-0-dev,
> omniorb4, omniidl4, omniorb4-nameserver, libomniorb4-1, libomniorb4-dev,
> libomnithread3-dev, libomnithread3c2 Priority: optional
> Section: unknown
> Filename:
> pool/main/r/ros-diamondback-orocos-toolchain-ros/ros-diamondback-orocos-too
> lchain-ros_0.2.1-s1299044547~lucid_i386.deb Size: 182689542
> SHA256: 79127c970eacba9f566cf9d9ff38cba49726d9b7c7f16f8bb157b8ae9f2c6c7f
> SHA1: 69e33cb252f3e62e5dc16fe259a52ade69390996
> MD5sum: fde1c3b1d4fc6c74b7886fcb7d10448a
> Description: orocos_toolchain_ros
> This stack contains all software necessary to build systems using both
> Orocos and ROS infrastructures. The complete Orocos Toolchain is integrated
> in the ROS build system and the rtt_ros_integration package allows easy
> communication between Orocos components and ROS nodes. Wg-Rosdistro:
> diamondback
>
>
> Cheers,
> Pierrick
>
> On Fri, Mar 4, 2011 at 4:49 PM, Peter Soetens
> <peter [..] ...<mailto:peter [..] ...>> wrote:
>
> On Friday 04 March 2011 10:26:12 Ruben Smits wrote:
> > On Friday 04 March 2011 09:51:52 Peter Soetens wrote:
> > > On Fri, Mar 4, 2011 at 4:26 AM, Pierrick Koch
> > > <pierrick [dot] koch [..] ...<mailto:pierrick [dot] koch [..] ...>>
> >
> > wrote:
> > > > Hello Orocos,
> > > > I am having an issue in starting using the
> > > > "orocos_toolchain_ros" on
> > > > ROS Diamondback.
> > > > I can't access orogen / or compil it:
> > > > $ rosmake orocos_toolchain_ros
> > > > ...
> > > > [rosmake-1] Starting >>> orogen [ make ]
> > > > [rosmake-1] Finished <<< orogen ROS_NOBUILD in package orogen
> > > > ...
> > > > there is ROS_NOBUILD files in all subdirectory... so I guess
> > > > it's
> > > > because I use the Debian packaged version .. but then:
> > > > $ rosrun orogen orogen
> > > > [rosrun] Couldn't find executable named orogen below
> > > > /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
> > > > [rosrun] Found the following, but they're either not files,
> > > > [rosrun] or not executable:
> > > > [rosrun]
> > > > /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
> > >
> > > You can't use rosrun to run orogen. First of all, orogen relies on a
> > > set of ruby gems which are not in the 'global path', so this needs
> > > to be set with the GEM_HOME and RUBYLIB directory. The
> > > orocos_toolchain_ros/env.sh file does that, and adds orogen to your
> > > PATH.
> > >
> > > Peter
> > >
> > > PS to others: couldn't we plant a 'dummy' orogen executable which is
> > > found by rosrun and which tells the user to source env.sh ? A next
> > > step
> > > could be that this file sources env.sh itself and then calls real
> > > orogen.
> >
> > Something like the following works for me:
> >
> > diff --git a/bin/ros_orogen.sh b/bin/ros_orogen.sh
> > new file mode 100755
> > index 0000000..8a6ec2a
> > --- /dev/null
> > +++ b/bin/ros_orogen.sh
> > @@ -0,0 +1,3 @@
> > +#!/bin/bash
> > +source `rosstack find orocos_toolchain_ros`/env.sh
> > +orogen $@
> > \ No newline at end of file
> > diff --git a/bin/ros_typegen.sh b/bin/ros_typegen.sh
> > new file mode 100755
> > index 0000000..8f0a77c
> > --- /dev/null
> > +++ b/bin/ros_typegen.sh
> > @@ -0,0 +1,3 @@
> > +#!/bin/bash
> > +source `rosstack find orocos_toolchain_ros`/env.sh
> > +typegen $@
> > \ No newline at end of file
>
> I would at least drop the '.sh' suffix from these filenames.
>
> On the other hand, I don't understand why this error message was given:
> > [rosrun] Couldn't find executable named orogen below
> > /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
> > [rosrun] Found the following, but they're either not files,
> > [rosrun] or not executable:
> > [rosrun] /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
>
> instead of:
>
> $ rosrun orogen orogen
> /home/kaltan/src/git/orocos-toolchain/orogen/bin/orogen:3:in `require': no
> such file to load -- orogen (LoadError)
> from /home/kaltan/src/git/orocos-toolchain/orogen/bin/orogen:3
>
>
> Which is what happens on my side when env.sh is not sourced.
>
> What are the contents of the
> /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen/bin directory
> on your system ??
>
> Peter
>
>
>
> --
> Pierrick Koch
> +841675357334 [UTC+7]
> Skype: pierrick.koch
> linkedin.com/in/pierriko<http://linkedin.com/in/pierriko>

orocos_toolchain_ros/orogen

Dear Ruben,

I got the master branch of the git repository and built it as:

cd $WORKING_DIR/ros
git clone http://git.mech.kuleuven.be/robotics/orocos_toolchain_ros.git
cd orocos_toolchain_ros
git checkout
git submodule init
git submodule update --recursive
export ROS_PACKAGE_PATH=$WORKING_DIR/ros/orocos_toolchain_ros:$ROS_PACKAGE_PATH
rosmake orocos_toolchain_ros

I was wondering if the build of orogen was suppose to take many hours..
[rosmake-1] Finished <<< rtt_ros_integration_nav_msgs [PASS] [ 181.02
seconds ]

[ rosmake ] [ make ] [ orogen: 3664.3 sec ] [ 1 Active 50/51
Complete ]
(and keep working without CPU activity) so after a while, I interrupt it
and:
$ orogen
Usage: [...]
*** glibc detected *** ruby: double free or corruption (fasttop): 0x08dba048
***
and any other call to orogen end up with this error...

thanks for your help,
Pierrick

On Mon, Mar 7, 2011 at 6:30 PM, Ruben Smits <ruben [dot] smits [..] ...>wrote:

> On Monday 07 March 2011 12:17:02 Pierrick Koch wrote:
> > Hi Peter,
> >
> > there is no bin folder in orogen, and a ROS_NO_BUILD file, that I guess
> is
> > here to prevent from (re)build... btw I'm on Ubuntu 10.04 (lucid) i686.
> >
> > $ ll /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
> > total 44
> > drwxr-xr-x 2 root root 4096 2011-03-03 15:27 ./
> > drwxr-xr-x 18 root root 4096 2011-03-03 15:27 ../
> > -rw-r--r-- 1 root root 1418 2011-02-07 19:21 CMakeLists.txt
> > -rw-r--r-- 1 root root 0 2011-03-02 12:51 gems
> > -rw-r--r-- 1 root root 584 2011-02-07 19:21 mainpage.dox
> > -rw-r--r-- 1 root root 586 2011-02-07 19:21 Makefile
> > -rw-r--r-- 1 root root 481 2011-02-07 19:21 Makefile.git
> > -rw-r--r-- 1 root root 720 2011-02-07 19:21 manifest.xml
> > -rw-r--r-- 1 root root 47 2011-02-07 19:21 orogen.md5sum
> > -rw-r--r-- 1 root root 3286 2011-02-07 19:21 orogen.patch
> > -rw-r--r-- 1 root root 1031 2011-02-07 19:21 README
> > -rw-r--r-- 1 root root 39 2011-03-02 13:27 ROS_NOBUILD
> >
>
> The debian package building definitely went wrong, since the package isn't
> build at all.
>
> Can you retry with master from git?
> http://git.mech.kuleuven.be/robotics/orocos_toolchain_ros.git.
>
> The version on git uses submodules instead of downloading the source like
> version 0.2.1. I'm in the middle of releasing 0.3.0 which will not have
> this
> issue and which will be in sync with toolchain 2.3
>
>
> -- Ruben
> >
> > the package infos are:
> >
> > $ apt-cache show ros-diamondback-orocos-toolchain-ros
> > Package: ros-diamondback-orocos-toolchain-ros
> > Version: 0.2.1-s1299044547~lucid
> > Architecture: i386
> > Maintainer: Ruben Smits - Steven Bellens
> > Installed-Size: 700884
> > Depends: ros-diamondback-ros (= 1.4.6-s1298587598~lucid),
> > ros-diamondback-ros-comm (= 1.4.5-s1299027150~lucid),
> > ros-diamondback-common-msgs (= 1.4.0-s1299027519~lucid), libc6,
> > build-essential, cmake, python-yaml, subversion, libboost1.40-all-dev,
> > libxslt1-dev, gccxml, libxml2-dev, antlr, libantlr-dev, ruby1.8-dev,
> > libopenssl-ruby1.8, rubygems1.8, libreadline-dev, liblua5.1-0-dev,
> > omniorb4, omniidl4, omniorb4-nameserver, libomniorb4-1, libomniorb4-dev,
> > libomnithread3-dev, libomnithread3c2 Priority: optional
> > Section: unknown
> > Filename:
> >
> pool/main/r/ros-diamondback-orocos-toolchain-ros/ros-diamondback-orocos-too
> > lchain-ros_0.2.1-s1299044547~lucid_i386.deb Size: 182689542
> > SHA256: 79127c970eacba9f566cf9d9ff38cba49726d9b7c7f16f8bb157b8ae9f2c6c7f
> > SHA1: 69e33cb252f3e62e5dc16fe259a52ade69390996
> > MD5sum: fde1c3b1d4fc6c74b7886fcb7d10448a
> > Description: orocos_toolchain_ros
> > This stack contains all software necessary to build systems using both
> > Orocos and ROS infrastructures. The complete Orocos Toolchain is
> integrated
> > in the ROS build system and the rtt_ros_integration package allows easy
> > communication between Orocos components and ROS nodes. Wg-Rosdistro:
> > diamondback
> >
> >
> > Cheers,
> > Pierrick
> >
> > On Fri, Mar 4, 2011 at 4:49 PM, Peter Soetens
> > <peter [..] ...<mailto:peter [..] ...>> wrote:
> >
> > On Friday 04 March 2011 10:26:12 Ruben Smits wrote:
> > > On Friday 04 March 2011 09:51:52 Peter Soetens wrote:
> > > > On Fri, Mar 4, 2011 at 4:26 AM, Pierrick Koch
> > > > <pierrick [dot] koch [..] ...<mailto:pierrick [dot] koch [..] ...>>
> > >
> > > wrote:
> > > > > Hello Orocos,
> > > > > I am having an issue in starting using the
> > > > > "orocos_toolchain_ros" on
> > > > > ROS Diamondback.
> > > > > I can't access orogen / or compil it:
> > > > > $ rosmake orocos_toolchain_ros
> > > > > ...
> > > > > [rosmake-1] Starting >>> orogen [ make ]
> > > > > [rosmake-1] Finished <<< orogen ROS_NOBUILD in package orogen
> > > > > ...
> > > > > there is ROS_NOBUILD files in all subdirectory... so I guess
> > > > > it's
> > > > > because I use the Debian packaged version .. but then:
> > > > > $ rosrun orogen orogen
> > > > > [rosrun] Couldn't find executable named orogen below
> > > > > /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
> > > > > [rosrun] Found the following, but they're either not files,
> > > > > [rosrun] or not executable:
> > > > > [rosrun]
> > > > > /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
> > > >
> > > > You can't use rosrun to run orogen. First of all, orogen relies on a
> > > > set of ruby gems which are not in the 'global path', so this needs
> > > > to be set with the GEM_HOME and RUBYLIB directory. The
> > > > orocos_toolchain_ros/env.sh file does that, and adds orogen to your
> > > > PATH.
> > > >
> > > > Peter
> > > >
> > > > PS to others: couldn't we plant a 'dummy' orogen executable which is
> > > > found by rosrun and which tells the user to source env.sh ? A next
> > > > step
> > > > could be that this file sources env.sh itself and then calls real
> > > > orogen.
> > >
> > > Something like the following works for me:
> > >
> > > diff --git a/bin/ros_orogen.sh b/bin/ros_orogen.sh
> > > new file mode 100755
> > > index 0000000..8a6ec2a
> > > --- /dev/null
> > > +++ b/bin/ros_orogen.sh
> > > @@ -0,0 +1,3 @@
> > > +#!/bin/bash
> > > +source `rosstack find orocos_toolchain_ros`/env.sh
> > > +orogen $@
> > > \ No newline at end of file
> > > diff --git a/bin/ros_typegen.sh b/bin/ros_typegen.sh
> > > new file mode 100755
> > > index 0000000..8f0a77c
> > > --- /dev/null
> > > +++ b/bin/ros_typegen.sh
> > > @@ -0,0 +1,3 @@
> > > +#!/bin/bash
> > > +source `rosstack find orocos_toolchain_ros`/env.sh
> > > +typegen $@
> > > \ No newline at end of file
> >
> > I would at least drop the '.sh' suffix from these filenames.
> >
> > On the other hand, I don't understand why this error message was given:
> > > [rosrun] Couldn't find executable named orogen below
> > > /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
> > > [rosrun] Found the following, but they're either not files,
> > > [rosrun] or not executable:
> > > [rosrun] /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
> >
> > instead of:
> >
> > $ rosrun orogen orogen
> > /home/kaltan/src/git/orocos-toolchain/orogen/bin/orogen:3:in `require':
> no
> > such file to load -- orogen (LoadError)
> > from /home/kaltan/src/git/orocos-toolchain/orogen/bin/orogen:3
> >
> >
> > Which is what happens on my side when env.sh is not sourced.
> >
> > What are the contents of the
> > /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen/bin directory
> > on your system ??
> >
> > Peter
> >
> >
> >
> > --
> > Pierrick Koch
> > +841675357334 [UTC+7]
> > Skype: pierrick.koch
> > linkedin.com/in/pierriko<http://linkedin.com/in/pierriko>
>

orocos_toolchain_ros/orogen

..ok, i just figure out that there was already a bug-repport
http://bugs.orocos.org/show_bug.cgi?id=828
It seems that the problem come from typelib.
I am runing Ubuntu 10.04 (lucid i686) with libboost 1.40, ros diamondback
from source [ rosinstall ~/ros "
http://packages.ros.org/cgi-bin/gen_rosinstall.py?rosdistro=diamondback&...
" ].

On Tue, Mar 15, 2011 at 12:34 PM, Pierrick Koch <pierrick [dot] koch [..] ...>wrote:

> Dear Ruben,
>
> I got the master branch of the git repository and built it as:
>
> cd $WORKING_DIR/ros
> git clone http://git.mech.kuleuven.be/robotics/orocos_toolchain_ros.git
> cd orocos_toolchain_ros
> git checkout
>
> git submodule init
> git submodule update --recursive
> export ROS_PACKAGE_PATH=$WORKING_DIR/ros/orocos_toolchain_ros:$ROS_PACKAGE_PATH
> rosmake orocos_toolchain_ros
>
> I was wondering if the build of orogen was suppose to take many hours..
> [rosmake-1] Finished <<< rtt_ros_integration_nav_msgs [PASS] [ 181.02
> seconds ]
>
> [ rosmake ] [ make ] [ orogen: 3664.3 sec ] [ 1 Active 50/51
> Complete ]
> (and keep working without CPU activity) so after a while, I interrupt it
> and:
> $ orogen
> Usage: [...]
> *** glibc detected *** ruby: double free or corruption (fasttop):
> 0x08dba048 ***
> and any other call to orogen end up with this error...
>
> thanks for your help,
> Pierrick
>
>
> On Mon, Mar 7, 2011 at 6:30 PM, Ruben Smits <ruben [dot] smits [..] ...>wrote:
>
>> On Monday 07 March 2011 12:17:02 Pierrick Koch wrote:
>> > Hi Peter,
>> >
>> > there is no bin folder in orogen, and a ROS_NO_BUILD file, that I guess
>> is
>> > here to prevent from (re)build... btw I'm on Ubuntu 10.04 (lucid) i686.
>> >
>> > $ ll /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
>> > total 44
>> > drwxr-xr-x 2 root root 4096 2011-03-03 15:27 ./
>> > drwxr-xr-x 18 root root 4096 2011-03-03 15:27 ../
>> > -rw-r--r-- 1 root root 1418 2011-02-07 19:21 CMakeLists.txt
>> > -rw-r--r-- 1 root root 0 2011-03-02 12:51 gems
>> > -rw-r--r-- 1 root root 584 2011-02-07 19:21 mainpage.dox
>> > -rw-r--r-- 1 root root 586 2011-02-07 19:21 Makefile
>> > -rw-r--r-- 1 root root 481 2011-02-07 19:21 Makefile.git
>> > -rw-r--r-- 1 root root 720 2011-02-07 19:21 manifest.xml
>> > -rw-r--r-- 1 root root 47 2011-02-07 19:21 orogen.md5sum
>> > -rw-r--r-- 1 root root 3286 2011-02-07 19:21 orogen.patch
>> > -rw-r--r-- 1 root root 1031 2011-02-07 19:21 README
>> > -rw-r--r-- 1 root root 39 2011-03-02 13:27 ROS_NOBUILD
>> >
>>
>> The debian package building definitely went wrong, since the package isn't
>> build at all.
>>
>> Can you retry with master from git?
>> http://git.mech.kuleuven.be/robotics/orocos_toolchain_ros.git.
>>
>> The version on git uses submodules instead of downloading the source like
>> version 0.2.1. I'm in the middle of releasing 0.3.0 which will not have
>> this
>> issue and which will be in sync with toolchain 2.3
>>
>>
>> -- Ruben
>> >
>> > the package infos are:
>> >
>> > $ apt-cache show ros-diamondback-orocos-toolchain-ros
>> > Package: ros-diamondback-orocos-toolchain-ros
>> > Version: 0.2.1-s1299044547~lucid
>> > Architecture: i386
>> > Maintainer: Ruben Smits - Steven Bellens
>> > Installed-Size: 700884
>> > Depends: ros-diamondback-ros (= 1.4.6-s1298587598~lucid),
>> > ros-diamondback-ros-comm (= 1.4.5-s1299027150~lucid),
>> > ros-diamondback-common-msgs (= 1.4.0-s1299027519~lucid), libc6,
>> > build-essential, cmake, python-yaml, subversion, libboost1.40-all-dev,
>> > libxslt1-dev, gccxml, libxml2-dev, antlr, libantlr-dev, ruby1.8-dev,
>> > libopenssl-ruby1.8, rubygems1.8, libreadline-dev, liblua5.1-0-dev,
>> > omniorb4, omniidl4, omniorb4-nameserver, libomniorb4-1, libomniorb4-dev,
>> > libomnithread3-dev, libomnithread3c2 Priority: optional
>> > Section: unknown
>> > Filename:
>> >
>> pool/main/r/ros-diamondback-orocos-toolchain-ros/ros-diamondback-orocos-too
>> > lchain-ros_0.2.1-s1299044547~lucid_i386.deb Size: 182689542
>> > SHA256: 79127c970eacba9f566cf9d9ff38cba49726d9b7c7f16f8bb157b8ae9f2c6c7f
>> > SHA1: 69e33cb252f3e62e5dc16fe259a52ade69390996
>> > MD5sum: fde1c3b1d4fc6c74b7886fcb7d10448a
>> > Description: orocos_toolchain_ros
>> > This stack contains all software necessary to build systems using both
>> > Orocos and ROS infrastructures. The complete Orocos Toolchain is
>> integrated
>> > in the ROS build system and the rtt_ros_integration package allows easy
>> > communication between Orocos components and ROS nodes. Wg-Rosdistro:
>> > diamondback
>> >
>> >
>> > Cheers,
>> > Pierrick
>> >
>> > On Fri, Mar 4, 2011 at 4:49 PM, Peter Soetens
>> > <peter [..] ...<mailto:peter [..] ...>> wrote:
>> >
>> > On Friday 04 March 2011 10:26:12 Ruben Smits wrote:
>> > > On Friday 04 March 2011 09:51:52 Peter Soetens wrote:
>> > > > On Fri, Mar 4, 2011 at 4:26 AM, Pierrick Koch
>> > > > <pierrick [dot] koch [..] ...<mailto:pierrick [dot] koch [..] ...>>
>> > >
>> > > wrote:
>> > > > > Hello Orocos,
>> > > > > I am having an issue in starting using the
>> > > > > "orocos_toolchain_ros" on
>> > > > > ROS Diamondback.
>> > > > > I can't access orogen / or compil it:
>> > > > > $ rosmake orocos_toolchain_ros
>> > > > > ...
>> > > > > [rosmake-1] Starting >>> orogen [ make ]
>> > > > > [rosmake-1] Finished <<< orogen ROS_NOBUILD in package orogen
>> > > > > ...
>> > > > > there is ROS_NOBUILD files in all subdirectory... so I guess
>> > > > > it's
>> > > > > because I use the Debian packaged version .. but then:
>> > > > > $ rosrun orogen orogen
>> > > > > [rosrun] Couldn't find executable named orogen below
>> > > > > /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
>> > > > > [rosrun] Found the following, but they're either not files,
>> > > > > [rosrun] or not executable:
>> > > > > [rosrun]
>> > > > > /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
>> > > >
>> > > > You can't use rosrun to run orogen. First of all, orogen relies on a
>> > > > set of ruby gems which are not in the 'global path', so this needs
>> > > > to be set with the GEM_HOME and RUBYLIB directory. The
>> > > > orocos_toolchain_ros/env.sh file does that, and adds orogen to your
>> > > > PATH.
>> > > >
>> > > > Peter
>> > > >
>> > > > PS to others: couldn't we plant a 'dummy' orogen executable which is
>> > > > found by rosrun and which tells the user to source env.sh ? A next
>> > > > step
>> > > > could be that this file sources env.sh itself and then calls real
>> > > > orogen.
>> > >
>> > > Something like the following works for me:
>> > >
>> > > diff --git a/bin/ros_orogen.sh b/bin/ros_orogen.sh
>> > > new file mode 100755
>> > > index 0000000..8a6ec2a
>> > > --- /dev/null
>> > > +++ b/bin/ros_orogen.sh
>> > > @@ -0,0 +1,3 @@
>> > > +#!/bin/bash
>> > > +source `rosstack find orocos_toolchain_ros`/env.sh
>> > > +orogen $@
>> > > \ No newline at end of file
>> > > diff --git a/bin/ros_typegen.sh b/bin/ros_typegen.sh
>> > > new file mode 100755
>> > > index 0000000..8f0a77c
>> > > --- /dev/null
>> > > +++ b/bin/ros_typegen.sh
>> > > @@ -0,0 +1,3 @@
>> > > +#!/bin/bash
>> > > +source `rosstack find orocos_toolchain_ros`/env.sh
>> > > +typegen $@
>> > > \ No newline at end of file
>> >
>> > I would at least drop the '.sh' suffix from these filenames.
>> >
>> > On the other hand, I don't understand why this error message was given:
>> > > [rosrun] Couldn't find executable named orogen below
>> > > /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
>> > > [rosrun] Found the following, but they're either not files,
>> > > [rosrun] or not executable:
>> > > [rosrun] /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
>> >
>> > instead of:
>> >
>> > $ rosrun orogen orogen
>> > /home/kaltan/src/git/orocos-toolchain/orogen/bin/orogen:3:in `require':
>> no
>> > such file to load -- orogen (LoadError)
>> > from /home/kaltan/src/git/orocos-toolchain/orogen/bin/orogen:3
>> >
>> >
>> > Which is what happens on my side when env.sh is not sourced.
>> >
>> > What are the contents of the
>> > /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen/bin directory
>> > on your system ??
>> >
>> > Peter
>> >
>> >
>> >
>> > --
>> > Pierrick Koch
>> > +841675357334 [UTC+7]
>> > Skype: pierrick.koch
>> > linkedin.com/in/pierriko<http://linkedin.com/in/pierriko>
>>
>
>
>
> --
> Pierrick Koch
> +841675357334 [UTC+7]
> *linkedin.com/in/pierriko* <http://linkedin.com/in/pierriko>
>
>

orocos_toolchain_ros/orogen

I think orogen is not currently "supposed" to work in a ROS_ROOT install.

2011/3/15 Pierrick Koch <pierrick [dot] koch [..] ...>

> ..ok, i just figure out that there was already a bug-repport
> http://bugs.orocos.org/show_bug.cgi?id=828
> It seems that the problem come from typelib.
> I am runing Ubuntu 10.04 (lucid i686) with libboost 1.40, ros diamondback
> from source [ rosinstall ~/ros "
> http://packages.ros.org/cgi-bin/gen_rosinstall.py?rosdistro=diamondback&...
> " ].
>
>
>
> On Tue, Mar 15, 2011 at 12:34 PM, Pierrick Koch <pierrick [dot] koch [..] ...>wrote:
>
>> Dear Ruben,
>>
>> I got the master branch of the git repository and built it as:
>>
>> cd $WORKING_DIR/ros
>>
>> git clone http://git.mech.kuleuven.be/robotics/orocos_toolchain_ros.git
>>
>> cd orocos_toolchain_ros
>>
>> git checkout
>>
>>
>> git submodule init
>> git submodule update --recursive
>>
>> export ROS_PACKAGE_PATH=$WORKING_DIR/ros/orocos_toolchain_ros:$ROS_PACKAGE_PATH
>>
>> rosmake orocos_toolchain_ros
>>
>> I was wondering if the build of orogen was suppose to take many hours..
>> [rosmake-1] Finished <<< rtt_ros_integration_nav_msgs [PASS] [ 181.02
>> seconds ]
>>
>> [ rosmake ] [ make ] [ orogen: 3664.3 sec ] [ 1 Active 50/51
>> Complete ]
>> (and keep working without CPU activity) so after a while, I interrupt it
>> and:
>> $ orogen
>> Usage: [...]
>> *** glibc detected *** ruby: double free or corruption (fasttop):
>> 0x08dba048 ***
>> and any other call to orogen end up with this error...
>>
>> thanks for your help,
>> Pierrick
>>
>>
>> On Mon, Mar 7, 2011 at 6:30 PM, Ruben Smits <ruben [dot] smits [..] ...
>> > wrote:
>>
>>> On Monday 07 March 2011 12:17:02 Pierrick Koch wrote:
>>> > Hi Peter,
>>> >
>>> > there is no bin folder in orogen, and a ROS_NO_BUILD file, that I guess
>>> is
>>> > here to prevent from (re)build... btw I'm on Ubuntu 10.04 (lucid) i686.
>>> >
>>> > $ ll /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
>>> > total 44
>>> > drwxr-xr-x 2 root root 4096 2011-03-03 15:27 ./
>>> > drwxr-xr-x 18 root root 4096 2011-03-03 15:27 ../
>>> > -rw-r--r-- 1 root root 1418 2011-02-07 19:21 CMakeLists.txt
>>> > -rw-r--r-- 1 root root 0 2011-03-02 12:51 gems
>>> > -rw-r--r-- 1 root root 584 2011-02-07 19:21 mainpage.dox
>>> > -rw-r--r-- 1 root root 586 2011-02-07 19:21 Makefile
>>> > -rw-r--r-- 1 root root 481 2011-02-07 19:21 Makefile.git
>>> > -rw-r--r-- 1 root root 720 2011-02-07 19:21 manifest.xml
>>> > -rw-r--r-- 1 root root 47 2011-02-07 19:21 orogen.md5sum
>>> > -rw-r--r-- 1 root root 3286 2011-02-07 19:21 orogen.patch
>>> > -rw-r--r-- 1 root root 1031 2011-02-07 19:21 README
>>> > -rw-r--r-- 1 root root 39 2011-03-02 13:27 ROS_NOBUILD
>>> >
>>>
>>> The debian package building definitely went wrong, since the package
>>> isn't
>>> build at all.
>>>
>>> Can you retry with master from git?
>>> http://git.mech.kuleuven.be/robotics/orocos_toolchain_ros.git.
>>>
>>> The version on git uses submodules instead of downloading the source like
>>> version 0.2.1. I'm in the middle of releasing 0.3.0 which will not have
>>> this
>>> issue and which will be in sync with toolchain 2.3
>>>
>>>
>>> -- Ruben
>>> >
>>> > the package infos are:
>>> >
>>> > $ apt-cache show ros-diamondback-orocos-toolchain-ros
>>> > Package: ros-diamondback-orocos-toolchain-ros
>>> > Version: 0.2.1-s1299044547~lucid
>>> > Architecture: i386
>>> > Maintainer: Ruben Smits - Steven Bellens
>>> > Installed-Size: 700884
>>> > Depends: ros-diamondback-ros (= 1.4.6-s1298587598~lucid),
>>> > ros-diamondback-ros-comm (= 1.4.5-s1299027150~lucid),
>>> > ros-diamondback-common-msgs (= 1.4.0-s1299027519~lucid), libc6,
>>> > build-essential, cmake, python-yaml, subversion, libboost1.40-all-dev,
>>> > libxslt1-dev, gccxml, libxml2-dev, antlr, libantlr-dev, ruby1.8-dev,
>>> > libopenssl-ruby1.8, rubygems1.8, libreadline-dev, liblua5.1-0-dev,
>>> > omniorb4, omniidl4, omniorb4-nameserver, libomniorb4-1,
>>> libomniorb4-dev,
>>> > libomnithread3-dev, libomnithread3c2 Priority: optional
>>> > Section: unknown
>>> > Filename:
>>> >
>>> pool/main/r/ros-diamondback-orocos-toolchain-ros/ros-diamondback-orocos-too
>>> > lchain-ros_0.2.1-s1299044547~lucid_i386.deb Size: 182689542
>>> > SHA256:
>>> 79127c970eacba9f566cf9d9ff38cba49726d9b7c7f16f8bb157b8ae9f2c6c7f
>>> > SHA1: 69e33cb252f3e62e5dc16fe259a52ade69390996
>>> > MD5sum: fde1c3b1d4fc6c74b7886fcb7d10448a
>>> > Description: orocos_toolchain_ros
>>> > This stack contains all software necessary to build systems using both
>>> > Orocos and ROS infrastructures. The complete Orocos Toolchain is
>>> integrated
>>> > in the ROS build system and the rtt_ros_integration package allows easy
>>> > communication between Orocos components and ROS nodes. Wg-Rosdistro:
>>> > diamondback
>>> >
>>> >
>>> > Cheers,
>>> > Pierrick
>>> >
>>> > On Fri, Mar 4, 2011 at 4:49 PM, Peter Soetens
>>> > <peter [..] ...<mailto:peter [..] ...>> wrote:
>>> >
>>> > On Friday 04 March 2011 10:26:12 Ruben Smits wrote:
>>> > > On Friday 04 March 2011 09:51:52 Peter Soetens wrote:
>>> > > > On Fri, Mar 4, 2011 at 4:26 AM, Pierrick Koch
>>> > > > <pierrick [dot] koch [..] ...<mailto:pierrick [dot] koch [..] ...>>
>>> > >
>>> > > wrote:
>>> > > > > Hello Orocos,
>>> > > > > I am having an issue in starting using the
>>> > > > > "orocos_toolchain_ros" on
>>> > > > > ROS Diamondback.
>>> > > > > I can't access orogen / or compil it:
>>> > > > > $ rosmake orocos_toolchain_ros
>>> > > > > ...
>>> > > > > [rosmake-1] Starting >>> orogen [ make ]
>>> > > > > [rosmake-1] Finished <<< orogen ROS_NOBUILD in package orogen
>>> > > > > ...
>>> > > > > there is ROS_NOBUILD files in all subdirectory... so I guess
>>> > > > > it's
>>> > > > > because I use the Debian packaged version .. but then:
>>> > > > > $ rosrun orogen orogen
>>> > > > > [rosrun] Couldn't find executable named orogen below
>>> > > > > /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
>>> > > > > [rosrun] Found the following, but they're either not files,
>>> > > > > [rosrun] or not executable:
>>> > > > > [rosrun]
>>> > > > > /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
>>> > > >
>>> > > > You can't use rosrun to run orogen. First of all, orogen relies on
>>> a
>>> > > > set of ruby gems which are not in the 'global path', so this needs
>>> > > > to be set with the GEM_HOME and RUBYLIB directory. The
>>> > > > orocos_toolchain_ros/env.sh file does that, and adds orogen to your
>>> > > > PATH.
>>> > > >
>>> > > > Peter
>>> > > >
>>> > > > PS to others: couldn't we plant a 'dummy' orogen executable which
>>> is
>>> > > > found by rosrun and which tells the user to source env.sh ? A next
>>> > > > step
>>> > > > could be that this file sources env.sh itself and then calls real
>>> > > > orogen.
>>> > >
>>> > > Something like the following works for me:
>>> > >
>>> > > diff --git a/bin/ros_orogen.sh b/bin/ros_orogen.sh
>>> > > new file mode 100755
>>> > > index 0000000..8a6ec2a
>>> > > --- /dev/null
>>> > > +++ b/bin/ros_orogen.sh
>>> > > @@ -0,0 +1,3 @@
>>> > > +#!/bin/bash
>>> > > +source `rosstack find orocos_toolchain_ros`/env.sh
>>> > > +orogen $@
>>> > > \ No newline at end of file
>>> > > diff --git a/bin/ros_typegen.sh b/bin/ros_typegen.sh
>>> > > new file mode 100755
>>> > > index 0000000..8f0a77c
>>> > > --- /dev/null
>>> > > +++ b/bin/ros_typegen.sh
>>> > > @@ -0,0 +1,3 @@
>>> > > +#!/bin/bash
>>> > > +source `rosstack find orocos_toolchain_ros`/env.sh
>>> > > +typegen $@
>>> > > \ No newline at end of file
>>> >
>>> > I would at least drop the '.sh' suffix from these filenames.
>>> >
>>> > On the other hand, I don't understand why this error message was given:
>>> > > [rosrun] Couldn't find executable named orogen below
>>> > > /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
>>> > > [rosrun] Found the following, but they're either not files,
>>> > > [rosrun] or not executable:
>>> > > [rosrun] /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
>>> >
>>> > instead of:
>>> >
>>> > $ rosrun orogen orogen
>>> > /home/kaltan/src/git/orocos-toolchain/orogen/bin/orogen:3:in `require':
>>> no
>>> > such file to load -- orogen (LoadError)
>>> > from /home/kaltan/src/git/orocos-toolchain/orogen/bin/orogen:3
>>> >
>>> >
>>> > Which is what happens on my side when env.sh is not sourced.
>>> >
>>> > What are the contents of the
>>> > /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen/bin directory
>>> > on your system ??
>>> >
>>> > Peter
>>> >
>>> >
>>> >
>>> > --
>>> > Pierrick Koch
>>> > +841675357334 [UTC+7]
>>> > Skype: pierrick.koch
>>> > linkedin.com/in/pierriko<http://linkedin.com/in/pierriko>
>>>
>>
>>
>>
>> --
>> Pierrick Koch
>> +841675357334 [UTC+7]
>> *linkedin.com/in/pierriko* <http://linkedin.com/in/pierriko>
>>
>>
>
>
> --
> Pierrick Koch
> +841675357334 [UTC+7]
> *linkedin.com/in/pierriko* <http://linkedin.com/in/pierriko>
>
>
> --
> Orocos-Users mailing list
> Orocos-Users [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>
>

orocos_toolchain_ros/orogen

maybe it could come from a "warning: array subscript is above array bounds"
?:

$ rosmake orocos_toolchain_ros --pre-clean

[rosmake-0] Starting >>> roslib [ make ]
> [ rosmake ] Output from build of package roslib written to: [ 1
> Active 8/48 Complete ]
> [ rosmake ]
> /home/proteus/.ros/rosmake/rosmake_output-20110316-153650/roslib/build_output.log
> [rosmake-0] Finished <<< roslib [PASS] [ 12.90 seconds ] -- WARNING: 1
> compiler warnings

make[3]: Entering directory `/home/proteus/work/ros/ros/core/roslib/build'
> [100%] Building CXX object CMakeFiles/roslib.dir/src/package.o
> /usr/include/c++/4.4/bits/stl_algo.h: In function ‘void
> ros::package::command(const std::string&, ros::package::V_string&)’:
> /usr/include/c++/4.4/bits/stl_algo.h:2178: warning: array subscript is
> above array bounds

Pierrick

On Tue, Mar 15, 2011 at 3:26 PM, Willy Lambert <lambert [dot] willy [..] ...>wrote:

> I think orogen is not currently "supposed" to work in a ROS_ROOT install.
>
> 2011/3/15 Pierrick Koch <pierrick [dot] koch [..] ...>
>
>> ..ok, i just figure out that there was already a bug-repport
>> http://bugs.orocos.org/show_bug.cgi?id=828
>> It seems that the problem come from typelib.
>> I am runing Ubuntu 10.04 (lucid i686) with libboost 1.40, ros diamondback
>> from source [ rosinstall ~/ros "
>> http://packages.ros.org/cgi-bin/gen_rosinstall.py?rosdistro=diamondback&...
>> " ].
>>
>>
>>
>> On Tue, Mar 15, 2011 at 12:34 PM, Pierrick Koch <pierrick [dot] koch [..] ...>wrote:
>>
>>> Dear Ruben,
>>>
>>> I got the master branch of the git repository and built it as:
>>>
>>> cd $WORKING_DIR/ros
>>>
>>>
>>>
>>>
>>>
>>> git clone http://git.mech.kuleuven.be/robotics/orocos_toolchain_ros.git
>>>
>>>
>>>
>>>
>>>
>>> cd orocos_toolchain_ros
>>>
>>> git checkout
>>>
>>>
>>> git submodule init
>>> git submodule update --recursive
>>>
>>> export ROS_PACKAGE_PATH=$WORKING_DIR/ros/orocos_toolchain_ros:$ROS_PACKAGE_PATH
>>>
>>>
>>>
>>>
>>>
>>> rosmake orocos_toolchain_ros
>>>
>>> I was wondering if the build of orogen was suppose to take many hours..
>>> [rosmake-1] Finished <<< rtt_ros_integration_nav_msgs [PASS] [ 181.02
>>> seconds ]
>>>
>>> [ rosmake ] [ make ] [ orogen: 3664.3 sec ] [ 1 Active 50/51
>>> Complete ]
>>> (and keep working without CPU activity) so after a while, I interrupt it
>>> and:
>>> $ orogen
>>> Usage: [...]
>>> *** glibc detected *** ruby: double free or corruption (fasttop):
>>> 0x08dba048 ***
>>> and any other call to orogen end up with this error...
>>>
>>> thanks for your help,
>>> Pierrick
>>>
>>>
>>> On Mon, Mar 7, 2011 at 6:30 PM, Ruben Smits <
>>> ruben [dot] smits [..] ...> wrote:
>>>
>>>> On Monday 07 March 2011 12:17:02 Pierrick Koch wrote:
>>>> > Hi Peter,
>>>> >
>>>> > there is no bin folder in orogen, and a ROS_NO_BUILD file, that I
>>>> guess is
>>>> > here to prevent from (re)build... btw I'm on Ubuntu 10.04 (lucid)
>>>> i686.
>>>> >
>>>> > $ ll /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
>>>> > total 44
>>>> > drwxr-xr-x 2 root root 4096 2011-03-03 15:27 ./
>>>> > drwxr-xr-x 18 root root 4096 2011-03-03 15:27 ../
>>>> > -rw-r--r-- 1 root root 1418 2011-02-07 19:21 CMakeLists.txt
>>>> > -rw-r--r-- 1 root root 0 2011-03-02 12:51 gems
>>>> > -rw-r--r-- 1 root root 584 2011-02-07 19:21 mainpage.dox
>>>> > -rw-r--r-- 1 root root 586 2011-02-07 19:21 Makefile
>>>> > -rw-r--r-- 1 root root 481 2011-02-07 19:21 Makefile.git
>>>> > -rw-r--r-- 1 root root 720 2011-02-07 19:21 manifest.xml
>>>> > -rw-r--r-- 1 root root 47 2011-02-07 19:21 orogen.md5sum
>>>> > -rw-r--r-- 1 root root 3286 2011-02-07 19:21 orogen.patch
>>>> > -rw-r--r-- 1 root root 1031 2011-02-07 19:21 README
>>>> > -rw-r--r-- 1 root root 39 2011-03-02 13:27 ROS_NOBUILD
>>>> >
>>>>
>>>> The debian package building definitely went wrong, since the package
>>>> isn't
>>>> build at all.
>>>>
>>>> Can you retry with master from git?
>>>> http://git.mech.kuleuven.be/robotics/orocos_toolchain_ros.git.
>>>>
>>>> The version on git uses submodules instead of downloading the source
>>>> like
>>>> version 0.2.1. I'm in the middle of releasing 0.3.0 which will not have
>>>> this
>>>> issue and which will be in sync with toolchain 2.3
>>>>
>>>>
>>>> -- Ruben
>>>> >
>>>> > the package infos are:
>>>> >
>>>> > $ apt-cache show ros-diamondback-orocos-toolchain-ros
>>>> > Package: ros-diamondback-orocos-toolchain-ros
>>>> > Version: 0.2.1-s1299044547~lucid
>>>> > Architecture: i386
>>>> > Maintainer: Ruben Smits - Steven Bellens
>>>> > Installed-Size: 700884
>>>> > Depends: ros-diamondback-ros (= 1.4.6-s1298587598~lucid),
>>>> > ros-diamondback-ros-comm (= 1.4.5-s1299027150~lucid),
>>>> > ros-diamondback-common-msgs (= 1.4.0-s1299027519~lucid), libc6,
>>>> > build-essential, cmake, python-yaml, subversion, libboost1.40-all-dev,
>>>> > libxslt1-dev, gccxml, libxml2-dev, antlr, libantlr-dev, ruby1.8-dev,
>>>> > libopenssl-ruby1.8, rubygems1.8, libreadline-dev, liblua5.1-0-dev,
>>>> > omniorb4, omniidl4, omniorb4-nameserver, libomniorb4-1,
>>>> libomniorb4-dev,
>>>> > libomnithread3-dev, libomnithread3c2 Priority: optional
>>>> > Section: unknown
>>>> > Filename:
>>>> >
>>>> pool/main/r/ros-diamondback-orocos-toolchain-ros/ros-diamondback-orocos-too
>>>> > lchain-ros_0.2.1-s1299044547~lucid_i386.deb Size: 182689542
>>>> > SHA256:
>>>> 79127c970eacba9f566cf9d9ff38cba49726d9b7c7f16f8bb157b8ae9f2c6c7f
>>>> > SHA1: 69e33cb252f3e62e5dc16fe259a52ade69390996
>>>> > MD5sum: fde1c3b1d4fc6c74b7886fcb7d10448a
>>>> > Description: orocos_toolchain_ros
>>>> > This stack contains all software necessary to build systems using
>>>> both
>>>> > Orocos and ROS infrastructures. The complete Orocos Toolchain is
>>>> integrated
>>>> > in the ROS build system and the rtt_ros_integration package allows
>>>> easy
>>>> > communication between Orocos components and ROS nodes. Wg-Rosdistro:
>>>> > diamondback
>>>> >
>>>> >
>>>> > Cheers,
>>>> > Pierrick
>>>> >
>>>> > On Fri, Mar 4, 2011 at 4:49 PM, Peter Soetens
>>>> > <peter [..] ...<mailto:peter [..] ...>> wrote:
>>>> >
>>>> > On Friday 04 March 2011 10:26:12 Ruben Smits wrote:
>>>> > > On Friday 04 March 2011 09:51:52 Peter Soetens wrote:
>>>> > > > On Fri, Mar 4, 2011 at 4:26 AM, Pierrick Koch
>>>> > > > <pierrick [dot] koch [..] ...<mailto:pierrick [dot] koch [..] ...>>
>>>> > >
>>>> > > wrote:
>>>> > > > > Hello Orocos,
>>>> > > > > I am having an issue in starting using the
>>>> > > > > "orocos_toolchain_ros" on
>>>> > > > > ROS Diamondback.
>>>> > > > > I can't access orogen / or compil it:
>>>> > > > > $ rosmake orocos_toolchain_ros
>>>> > > > > ...
>>>> > > > > [rosmake-1] Starting >>> orogen [ make ]
>>>> > > > > [rosmake-1] Finished <<< orogen ROS_NOBUILD in package orogen
>>>> > > > > ...
>>>> > > > > there is ROS_NOBUILD files in all subdirectory... so I guess
>>>> > > > > it's
>>>> > > > > because I use the Debian packaged version .. but then:
>>>> > > > > $ rosrun orogen orogen
>>>> > > > > [rosrun] Couldn't find executable named orogen below
>>>> > > > > /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
>>>> > > > > [rosrun] Found the following, but they're either not files,
>>>> > > > > [rosrun] or not executable:
>>>> > > > > [rosrun]
>>>> > > > > /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
>>>> > > >
>>>> > > > You can't use rosrun to run orogen. First of all, orogen relies on
>>>> a
>>>> > > > set of ruby gems which are not in the 'global path', so this needs
>>>> > > > to be set with the GEM_HOME and RUBYLIB directory. The
>>>> > > > orocos_toolchain_ros/env.sh file does that, and adds orogen to
>>>> your
>>>> > > > PATH.
>>>> > > >
>>>> > > > Peter
>>>> > > >
>>>> > > > PS to others: couldn't we plant a 'dummy' orogen executable which
>>>> is
>>>> > > > found by rosrun and which tells the user to source env.sh ? A next
>>>> > > > step
>>>> > > > could be that this file sources env.sh itself and then calls real
>>>> > > > orogen.
>>>> > >
>>>> > > Something like the following works for me:
>>>> > >
>>>> > > diff --git a/bin/ros_orogen.sh b/bin/ros_orogen.sh
>>>> > > new file mode 100755
>>>> > > index 0000000..8a6ec2a
>>>> > > --- /dev/null
>>>> > > +++ b/bin/ros_orogen.sh
>>>> > > @@ -0,0 +1,3 @@
>>>> > > +#!/bin/bash
>>>> > > +source `rosstack find orocos_toolchain_ros`/env.sh
>>>> > > +orogen $@
>>>> > > \ No newline at end of file
>>>> > > diff --git a/bin/ros_typegen.sh b/bin/ros_typegen.sh
>>>> > > new file mode 100755
>>>> > > index 0000000..8f0a77c
>>>> > > --- /dev/null
>>>> > > +++ b/bin/ros_typegen.sh
>>>> > > @@ -0,0 +1,3 @@
>>>> > > +#!/bin/bash
>>>> > > +source `rosstack find orocos_toolchain_ros`/env.sh
>>>> > > +typegen $@
>>>> > > \ No newline at end of file
>>>> >
>>>> > I would at least drop the '.sh' suffix from these filenames.
>>>> >
>>>> > On the other hand, I don't understand why this error message was
>>>> given:
>>>> > > [rosrun] Couldn't find executable named orogen below
>>>> > > /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
>>>> > > [rosrun] Found the following, but they're either not files,
>>>> > > [rosrun] or not executable:
>>>> > > [rosrun] /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
>>>> >
>>>> > instead of:
>>>> >
>>>> > $ rosrun orogen orogen
>>>> > /home/kaltan/src/git/orocos-toolchain/orogen/bin/orogen:3:in
>>>> `require': no
>>>> > such file to load -- orogen (LoadError)
>>>> > from /home/kaltan/src/git/orocos-toolchain/orogen/bin/orogen:3
>>>> >
>>>> >
>>>> > Which is what happens on my side when env.sh is not sourced.
>>>> >
>>>> > What are the contents of the
>>>> > /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen/bin directory
>>>> > on your system ??
>>>> >
>>>> > Peter
>>>> >
>>>> >
>>>> >
>>>> > --
>>>> > Pierrick Koch
>>>> > +841675357334 [UTC+7]
>>>> > Skype: pierrick.koch
>>>> > linkedin.com/in/pierriko<http://linkedin.com/in/pierriko>
>>>>
>>>
>>>
>>>
>>> --
>>> Pierrick Koch
>>> +841675357334 [UTC+7]
>>> *linkedin.com/in/pierriko* <http://linkedin.com/in/pierriko>
>>>
>>>
>>
>>
>> --
>> Pierrick Koch
>> +841675357334 [UTC+7]
>> *linkedin.com/in/pierriko* <http://linkedin.com/in/pierriko>
>>
>>
>> --
>> Orocos-Users mailing list
>> Orocos-Users [..] ...
>> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>>
>>
>

Ruben Smits's picture

orocos_toolchain_ros/orogen

On Friday 04 March 2011 04:26:54 Pierrick Koch wrote:
> Hello Orocos,
>
> I am having an issue in starting using the "orocos_toolchain_ros" on ROS
> Diamondback. I can't access orogen / or compil it:
> $ rosmake orocos_toolchain_ros
> ...
> [rosmake-1] Starting >>> orogen [ make ]
> [rosmake-1] Finished <<< orogen ROS_NOBUILD in package orogen
> ...
> there is ROS_NOBUILD files in all subdirectory... so I guess it's because I
> use the Debian packaged version .. but then: $ rosrun orogen orogen
> [rosrun] Couldn't find executable named orogen below
> /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen [rosrun] Found the
> following, but they're either not files,
> [rosrun] or not executable:
> [rosrun] /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
> and I guess I have what I need to make it working...
> $ tail ~/.bashrc
> # ROS
> source /opt/ros/diamondback/setup.bash
> # Orocos ROS
> source /opt/ros/diamondback/stacks/orocos_toolchain_ros/env.sh
> $ orogen
> No command 'orogen' found, ...
>
> I am quite new to the all thing so maybe my problem is obvious, and I missd
> something... for the ROS part I think I'm OK (
> http://www.ros.org/wiki/diamondback/Installation/Ubuntu ) then for Orocos I
> followed http://www.ros.org/wiki/orocos_toolchain_ros sudo apt-get install
> ros-diamondback-orocos-toolchain-ros
>
> did I miss something ?

Before you can use orogen you need to source the env.sh script which is in the
orocos_toolchain_ros stack.

> Cheers,
> Pierrick

-- Ruben

orocos_toolchain_ros/orogen

2011/3/4 Pierrick Koch <pierrick [dot] koch [..] ...>

> Hello Orocos,
>
> I am having an issue in starting using the "orocos_toolchain_ros" on ROS
> Diamondback.
> I can't access orogen / or compil it:
> $ rosmake orocos_toolchain_ros
> ...
> [rosmake-1] Starting >>> orogen [ make ]
> [rosmake-1] Finished <<< orogen ROS_NOBUILD in package orogen
> ...
> there is ROS_NOBUILD files in all subdirectory... so I guess it's because I
> use the Debian packaged version .. but then:
> $ rosrun orogen orogen
> [rosrun] Couldn't find executable named orogen below
> /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
> [rosrun] Found the following, but they're either not files,
> [rosrun] or not executable:
> [rosrun] /opt/ros/diamondback/stacks/orocos_toolchain_ros/orogen
> and I guess I have what I need to make it working...
> $ tail ~/.bashrc
> # ROS
> source /opt/ros/diamondback/setup.bash
> # Orocos ROS
> source /opt/ros/diamondback/stacks/orocos_toolchain_ros/env.sh
> $ orogen
> No command 'orogen' found, ...
>
> I am quite new to the all thing so maybe my problem is obvious, and I missd
> something...
> for the ROS part I think I'm OK (
> http://www.ros.org/wiki/diamondback/Installation/Ubuntu )
> then for Orocos I followed http://www.ros.org/wiki/orocos_toolchain_ros
> sudo apt-get install ros-diamondback-orocos-toolchain-ros
>
> did I miss something ?
>
> Cheers,
> Pierrick
>
> --
> Orocos-Users mailing list
> Orocos-Users [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>
>
When you say Debian packaged version, you mean you are on Ubuntu on use the
.deb files ? (just to be sure).

When you are installing .deb, I think you receive prebuild libraries and
binaries so you don't have (and shouldn't actually) to rosmake it. I think
theses ROS_NOBUILD are here in this purpose.

your bashrc seem correct but it miss the extension of ROS_PACKAGE_PATH. Have
you done it somewhere ?
ROS_PACKAGE_PATH=$ROS_PACKAGE_PATH:/opt/ros/orocos_toolchain_ros