> Understood. How can how 'reconfigure' such that I only do the basic
> stuff? autoproj build --reconfigure does not do the job.
> Should I just remove the directory and get the bootstrap.sh for the
> basic install?

As Matthias mentions, you need to switch the "root" autoproj configuration.

One way would be to delete the autoproj/ folder, download the
bootstrap.sh and run it.

Another way is to use autoproj switch-config (Matthias had a typo ...)

autoproj switch-config git git://gitorious.org/rock/buildconf.git

On 20.11.2012 09:11, Tinne De Laet wrote:
> On 11/19/2012 05:59 PM, Sylvain Joyeux wrote:
>> On 11/19/2012 04:36 PM, Tinne De Laet wrote:
>>> Installation instructions followed from
>>> http://rock-robotics.org/stable/documentation/installation.html.
>>> Using the full boostrap.sh (*to build all of Rock*, use this
>>> bootstrap.sh
>>> <http://gitorious.com/rock/buildconf-all/blobs/raw/master/bootstrap.sh>
>>> instead of the one listed above)
>>> System: ubuntu quantal
>>> g++ (Ubuntu/Linaro 4.7.2-2ubuntu1) 4.7.2
>> Mmmm ... Nice. Nobody ever used Rock on quantal ... Us poor Rock
>> developers stuck so far on 12.04. Of course, I should have guessed
>> that the first nice person wanting to try it out would fall for that
>> ... :P
>>
>> On another note, I think I will really have to add a big fat fat
>> warning. When we say "all of rock", it is meant every single package
>> within Rock. I am not sure that it is very recommended if what you
>> want is simply "to get a feel for the stuff" ... and especially only
>> looking for e.g. the tutorials.
> Understood. How can how 'reconfigure' such that I only do the basic
> stuff? autoproj build --reconfigure does not do the job.
> Should I just remove the directory and get the bootstrap.sh for the
> basic install?

What do you mean by reconfigure,
if you would like to switch the package set, you could do this by:

autoproj switch-config git git://gitorious.org/rock/buildconfig.git

If you would only add some packages or package set you can simply add
them in your autoproj/manifest
For example if you would build all tutorials simply add under package_sets:

- gitorious: rock-tutorials/package_set

and in the layout section:

- rock.tutorials

After than an autoproj update && autoproj build instals all additional
packages without an "reconfiguration"

>>> Errors:
>>> * make
>>> compiling swap.cc
>>> make: g++: Command not found
>>> make: *** [swap.o] Error 127
>>> Gem files will remain installed in
>>> /home/tdelaet/rock/.gems/gems/utilrb-1.6.6 for inspection.
>>> Results logged to
>>> /home/tdelaet/rock/.gems/gems/utilrb-1.6.6/ext/gem_make.out
>>> ERROR: failed to run gem1.9.1 install --no-rdoc --no-ri autobuild
>>> ERROR: command output is: Building native extensions. This could take a
>>> while...
>>>
>>> => solved by installing g++ "sudo aptitude install g++
>> Interesting, it seems that even my fresh virtual machines are not-so
>> fresh ... and have g++ installed.
>>> * If you select you want to be compatible with existing ocl components
>>> but RTT is currently not installed on your computer, the installation
>>> fails
>>> (retried without choosing option to be compatible)
>> Worked for me. Can you give a more detailed error ?
> I currently can not reproduce this one anymore. The first error I get is
> the link error of pthread.

Fell free in general to post bugs if you can reproduce them to
rock.opendfki.de

>>> * Build failed
>>> drivers/iodrivers_base(/home/tdelaet/rock/drivers/iodrivers_base):
>>> failed in build phase
>>> 'make --jobserver-fds=5,6 -j' returned status 2
>>> see /home/tdelaet/rock/install/log/drivers/iodrivers_base-build.log for
>>> details
>>> last 10 lines are:
>>>
>>> Scanning dependencies of target test_tcp_read
>>> [ 75%] Building CXX object
>>> test/CMakeFiles/test_tcp_read.dir/test_tcp_read.cpp.o
>>> Linking CXX executable test_tcp_read
>>> ../src/libiodrivers_base.so: undefined reference to
>>> `pthread_mutexattr_settype'
>>> ../src/libiodrivers_base.so: undefined reference to
>>> `pthread_mutexattr_destroy'
>>> ../src/libiodrivers_base.so: undefined reference to
>>> `pthread_mutexattr_init'
>>> collect2: error: ld returned 1 exit status
>>> make[2]: *** [test/test_tcp_read] Error 1
>>> make[1]: *** [test/CMakeFiles/test_tcp_read.dir/all] Error 2
>>> make: *** [all] Error 2
>>>
>>> => Solution is probably to explictly add -lpthread, but to which file
>>> should this be added?
>> In principle, we should not have to. The library is properly linked to
>> boost thread, which is all we should need. I'll have to get myself a
>> clean quantal VM to do some testing.
>>
> Thanks for the help,

Youre welcome
>
> Tinne
>

Matthias

On 11/19/2012 06:04 PM, Thomas Roehr wrote:
> On 19.11.2012 17:59, Sylvain Joyeux wrote:
>> On 11/19/2012 04:36 PM, Tinne De Laet wrote:
>>> Installation instructions followed from
>>> http://rock-robotics.org/stable/documentation/installation.html.
>>> Using the full boostrap.sh (*to build all of Rock*, use this
>>> bootstrap.sh
>>> <http://gitorious.com/rock/buildconf-all/blobs/raw/master/bootstrap.sh>
>>> instead of the one listed above)
>>> System: ubuntu quantal
>>> g++ (Ubuntu/Linaro 4.7.2-2ubuntu1) 4.7.2
>> Mmmm ... Nice. Nobody ever used Rock on quantal ... Us poor Rock
>> developers stuck so far on 12.04. Of course, I should have guessed that
>> the first nice person wanting to try it out would fall for that ... :P
>>
>> On another note, I think I will really have to add a big fat fat
>> warning. When we say "all of rock", it is meant every single package
>> within Rock. I am not sure that it is very recommended if what you want
>> is simply "to get a feel for the stuff" ... and especially only looking
>> for e.g. the tutorials.
>>> Errors:
>>> * make
>>> compiling swap.cc
>>> make: g++: Command not found
>>> make: *** [swap.o] Error 127
>>> Gem files will remain installed in
>>> /home/tdelaet/rock/.gems/gems/utilrb-1.6.6 for inspection.
>>> Results logged to
>>> /home/tdelaet/rock/.gems/gems/utilrb-1.6.6/ext/gem_make.out
>>> ERROR: failed to run gem1.9.1 install --no-rdoc --no-ri autobuild
>>> ERROR: command output is: Building native extensions. This could take a
>>> while...
>>>
>>> => solved by installing g++ "sudo aptitude install g++
>> Interesting, it seems that even my fresh virtual machines are not-so
>> fresh ... and have g++ installed.
>>> * If you select you want to be compatible with existing ocl components
>>> but RTT is currently not installed on your computer, the
>>> installation fails
>>> (retried without choosing option to be compatible)
>> Worked for me. Can you give a more detailed error ?
>>> * Build failed
>>> drivers/iodrivers_base(/home/tdelaet/rock/drivers/iodrivers_base):
>>> failed in build phase
>>> 'make --jobserver-fds=5,6 -j' returned status 2
>>> see /home/tdelaet/rock/install/log/drivers/iodrivers_base-build.log for
>>> details
>>> last 10 lines are:
>>>
>>> Scanning dependencies of target test_tcp_read
>>> [ 75%] Building CXX object
>>> test/CMakeFiles/test_tcp_read.dir/test_tcp_read.cpp.o
>>> Linking CXX executable test_tcp_read
>>> ../src/libiodrivers_base.so: undefined reference to
>>> `pthread_mutexattr_settype'
>>> ../src/libiodrivers_base.so: undefined reference to
>>> `pthread_mutexattr_destroy'
>>> ../src/libiodrivers_base.so: undefined reference to
>>> `pthread_mutexattr_init'
>>> collect2: error: ld returned 1 exit status
>>> make[2]: *** [test/test_tcp_read] Error 1
>>> make[1]: *** [test/CMakeFiles/test_tcp_read.dir/all] Error 2
>>> make: *** [all] Error 2
>>>
>>> => Solution is probably to explictly add -lpthread, but to which file
>>> should this be added?
>> In principle, we should not have to. The library is properly linked to
>> boost thread, which is all we should need. I'll have to get myself a
>> clean quantal VM to do some testing.
> For now to proceed try adding to src/CMakeList.txt the following line
> after the rock_library statement:
>
> target_link_libraries(iodrivers_base pthread)

That solved the error thanks!

Tinne