> In the meantime, your best bet is to make the paths on the build and
> host systems identical (you could use chroot on the build system to
> make this easier).

I had this same problem, and i can confirm that the above suggestion is the right way to go about it.
I successfully got Ros working on the gumstix.



On Fri, Apr 9, 2010 at 11:52 AM, Daniel Maier <maierd@informatik.uni-freiburg.de> wrote:
On Wed, 07 Apr 2010 06:32:08 +0200, Brian Gerkey <gerkey@willowgarage.com>
wrote:

> Cross-compiling is not well-exercised or supported in ROS at the
> moment, and you've come across one of the frailties of the current
> state of affairs.  A common approach when cross-compiling is to
> statically link executables, to avoid even copying the object files to
> the embeddd system, much less finding them at run time.  But I'm
> pretty sure that the ROS build system won't properly link static
> executables at the moment.
>
> What you really want is to be able to *install* your ROS system after
> building it.  The install step is on the roadmap for the ROS 1.1.x
> series; I'll keep the cross-compilation use-case in mind when
> designing it.
>
> In the meantime, your best bet is to make the paths on the build and
> host systems identical (you could use chroot on the build system to
> make this easier).
>
>       brian.
>

Ok, will do it that way. Thanks Brian!
_______________________________________________
ros-users mailing list
ros-users@code.ros.org
https://code.ros.org/mailman/listinfo/ros-users