| 2015-06-02 16:04:51 -0500 | received badge | ● Taxonomist |
| 2014-07-06 03:00:01 -0500 | received badge | ● Citizen Patrol (source) |
| 2013-06-27 03:58:54 -0500 | received badge | ● Notable Question (source) |
| 2013-06-27 03:58:54 -0500 | received badge | ● Popular Question (source) |
| 2013-06-27 03:58:54 -0500 | received badge | ● Famous Question (source) |
| 2013-01-15 02:29:31 -0500 | received badge | ● Famous Question (source) |
| 2013-01-08 03:24:09 -0500 | received badge | ● Self-Learner (source) |
| 2013-01-08 03:24:09 -0500 | received badge | ● Teacher (source) |
| 2013-01-07 18:59:51 -0500 | received badge | ● Supporter (source) |
| 2013-01-07 18:59:18 -0500 | answered a question | Error "unknown address family 10" in roslaunch's ProcessMonitor ROS Groovy seems to require python with IPv6 support in constrast to the previous versions (fuerte, electric, ...). After installing python with IPv6 support (--enable-ipv6), the issue was resolved. |
| 2013-01-07 18:56:31 -0500 | received badge | ● Scholar (source) |
| 2013-01-07 08:41:06 -0500 | received badge | ● Nice Question (source) |
| 2013-01-07 02:49:07 -0500 | asked a question | Error "unknown address family 10" in roslaunch's ProcessMonitor Hi all, I wanted to switch from fuerte to groovy on my virtual machine. After I have successfully compiled all ros_comm packages, I started roscore, but it terminates at startup with the error message: unknown address family 10 in the roslaunch/pymon.py. The system is a custom Linux system (compiled with openembedded) and Python 2.7.3. NB: As it a custom Linux system, I did not use rosdep to resolve the system dependencies, but tried to resolve it manually. Googling for the error above did not give a valuable hint what I am doing wrong. Does anyone have a clue? The full logfile is at http://pastebin.com/mxNkHBHS. Lukas Bulwahn BMW Car IT GmbH Petuelring 116 D-80809 Muenchen Germany Mail: lukas.bulwahn@bmw-carit.de Web: http://www.bmw-carit.de BMW Car IT GmbH Geschäftsführer: Harald Heinecke Sitz und Registergericht: München HRB134810 |
| 2012-12-06 14:32:19 -0500 | received badge | ● Good Question (source) |
| 2012-12-06 08:21:02 -0500 | received badge | ● Nice Question (source) |
| 2012-12-06 08:19:04 -0500 | received badge | ● Notable Question (source) |
| 2012-12-06 02:02:54 -0500 | received badge | ● Editor (source) |
| 2012-12-06 02:02:28 -0500 | answered a question | ROS Core build on arch Linux The answer from Lorenz is correct, but Lorenz was pointing at the development version where things have been fixed. However in the fuerte release version, it is not fixed. Nevertheless, simply apply the patch http://pastebin.com/ZFDD4Qhs in your ros_comm directory. |
| 2012-12-05 22:58:26 -0500 | commented answer | ROS Core build on arch Linux I did not understand the answer either before looking at https://github.com/ros/ros_comm/issues/10 |
| 2012-12-05 22:58:02 -0500 | commented question | ROS Core build on arch Linux I encountered the same problem when installing ROS from the sources with rosinstall. |
| 2012-11-29 22:06:35 -0500 | received badge | ● Popular Question (source) |
| 2012-11-19 06:23:15 -0500 | received badge | ● Student (source) |
| 2012-11-19 05:11:21 -0500 | asked a question | Packaging ROS for yocto or OpenEmbedded (using bitbake recipes) Hi, we are interested in setting up a computing platform for our development using linux with yocto (or OpenEmbedded-Core) and the robotic operating system ROS. We are currently at the very beginning of this development: As a first step, we want to package ROS for our own needs, but we are open to contribute this to the community if there are others that need this as well. Has someone in the community already packaged ROS for yocto or OpenEmbedded? Are there others that also interested in a ROS package for yocto or OpenEmbedded? We are happy about any feedback. Lukas Bulwahn BMW Car IT GmbH Petuelring 116 D-80809 Muenchen Germany BMW Car IT GmbH Geschäftsführer: Harald Heinecke Sitz und Registergericht: München HRB134810 |
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.