On 12/14/2010 10:07 AM, Peter Soetens wrote:
> On Monday 13 December 2010 19:06:17 gprizzi [..] ... wrote:
>> Dear sirs,
>>
>> I tried to install Toolchain 2.2. on Ubuntu using the following commands:
>>
>> mkdir orocos-toolchain
>> cd orocos-toolchain
>> wget
>> http://gitorious.com/orocos-toolchain/build/blobs/raw/toolchain-2.2/bootst
>> rap.sh sh bootstrap.sh
>>
>> but installation fails on Lua as you can see from the below error messages.
>>
>> What have I to do to complete installation?
>>
>> Thank you for your support.
>>
>> Gianpaolo Rizzi
>>
>>
>>
>> root@UBU1004:/usr/src/orocos-toolchain# wget
>> http://gitorious.com/orocos-toolchain/build/blobs/raw/toolchain-2.2/bootst
>> rap.sh --2010-12-13 17:28:53--
>> http://gitorious.com/orocos-toolchain/build/blobs/raw/toolchain-2.2/bootst
>> rap.sh Resolving gitorious.com... 87.238.52.168
>> Connecting to gitorious.com|87.238.52.168|:80... connected.
>> HTTP request sent, awaiting response... 200 OK
>> Cookie coming from gitorious.com attempted to set domain to gitorious.com
>> Length: 589 [application/sh]
>> Saving to: `bootstrap.sh'
>>
>> 100%[======================================================================
>> =========>] 589 --.-K/s in 0s
>>
>> 2010-12-13 17:28:54 (33.3 MB/s) - `bootstrap.sh' saved [589/589]
>>
>> root@UBU1004:/usr/src/orocos-toolchain# sn bootstrap.sh
>> The program 'sn' is currently not installed. You can install it by typing:
>> apt-get install mono-devel
>> root@UBU1004:/usr/src/orocos-toolchain# sh bootstrap.sh
>> --2010-12-13 17:29:13--
>> http://doudou.github.com/autoproj/autoproj_bootstrap Resolving
>> doudou.github.com... 207.97.227.245
>> Connecting to doudou.github.com|207.97.227.245|:80... connected.
>> HTTP request sent, awaiting response... 200 OK
>> Length: 52153 (51K) [application/octet-stream]
>> Saving to: `autoproj_bootstrap'
>>
>> 100%[======================================================================
>> =========>] 52,153 107K/s in 0.5s
>>
>> 2010-12-13 17:29:15 (107 KB/s) - `autoproj_bootstrap' saved [52153/52153]
>>
>> The current directory is not empty, continue bootstrapping anyway ? [yes]
>> autodetecting the operating system
>> Which prepackaged software (a.k.a. 'osdeps') should autoproj install
>> automatically (all, ruby, os, none) ? The software packages that autoproj
>> will have to build may require other prepackaged softwares (a.k.a. OS
>> dependencies) to be installed (RubyGems packages, packages from your
>> operating system/distribution, ...). Autoproj is able to install those
>> automatically for you.
>>
>> Advanced users may want to control this behaviour. Additionally, the
>> installation of some packages require administration rights, which you
>> may not have. This option is meant to allow you to control autoproj's
>> behaviour while handling OS dependencies.
>>
>> * if you say "all", it will install all packages automatically.
>> This requires root access thru 'sudo'
>> * if you say "ruby", only the Ruby packages will be installed.
>> Installing these packages does not require root access.
>> * if you say "os", only the OS-provided packages will be installed.
>> Installing these packages requires root access.
>> * if you say "none", autoproj will not do anything related to the
>> OS dependencies.
>>
>> As any configuration value, the mode can be changed anytime by calling
>> an autoproj operation with the --reconfigure option (e.g. autoproj
>> update --reconfigure).
>>
>> Finally, OS dependencies can be installed by calling "autoproj osdeps"
>> with the corresponding option (--all, --ruby, --os or --none). [all]
>> autoproj: installing a proper Ruby environment (this can take a long time)
>> autoproj: installing autoproj and its dependencies (this can take a long
>> time) installing/updating RubyGems dependencies: autobuild, rdoc
>> Enclosing class/module 'mUtilrb' for class WeakRef not known
>> Enclosing class/module 'cWeakRef' for class RefError not known
>> Enclosing class/module 'mUtilrb' for class WeakRef not known
>> Enclosing class/module 'cWeakRef' for class RefError not known
>> installing/updating RubyGems dependencies: autoproj
>> autodetecting the operating system
>> checking out autoproj main configuration
>> Access method to gitorious (git, http or ssh)
>> Use 'ssh' only if you have a gitorious account and have commit rights
>> on the Orocos projects. Otherwise, we advise you to use 'git' [git]
>> Which prepackaged software (a.k.a. 'osdeps') should autoproj install
>> automatically (all, ruby, os, none) ? all autoproj: updating remote
>> definitions of package sets
>> checking out git:git://gitorious.org//orocos-toolchain/autoproj.git
>> branch=toolchain-2.2
>>
>> autoproj: loading ...
>> run 'autoproj reconfigure' to change configuration options
>> and use 'autoproj switch-config' to change the remote source for
>> autoproj's main build configuration
>> the target operating system for Orocos/RTT (gnulinux or xenomai)
>> [gnulinux] which CORBA implementation should the RTT use ?
>> Answer 'none' to disable CORBA, otherwise pick either tao or omniorb
>> [omniorb]
>>
>> autoproj: package sets
>> orocos.toolchain (listed in manifest)
>> from: git:git://gitorious.org//orocos-toolchain/autoproj.git
>> branch=toolchain-2.2 local:
>> /usr/src/orocos-toolchain/autoproj/remotes/orocos.toolchain defines:
>> log4cpp, ocl, orogen, rtt, typelib, utilmm, utilrb
>>
>> autoproj: packages
>> log4cpp
>> defined in orocos.toolchain
>> will be checked out in /usr/src/orocos-toolchain/log4cpp
>> git:git://gitorious.org//orocos-toolchain/log4cpp.git
>> branch=toolchain-2.2 NOT checked out yet, reported dependencies will be
>> partial
>> ocl
>> defined in orocos.toolchain
>> will be checked out in /usr/src/orocos-toolchain/ocl
>> git:git://gitorious.org//orocos-toolchain/ocl.git branch=toolchain-2.2
>> NOT checked out yet, reported dependencies will be partial
>> orogen
>> defined in orocos.toolchain
>> will be checked out in /usr/src/orocos-toolchain/orogen
>> git:git://gitorious.org//orocos-toolchain/orogen.git
>> branch=toolchain-2.2 NOT checked out yet, reported dependencies will be
>> partial
>> rtt
>> defined in orocos.toolchain
>> will be checked out in /usr/src/orocos-toolchain/rtt
>> git:git://gitorious.org//orocos-toolchain/rtt.git branch=toolchain-2.2
>> NOT checked out yet, reported dependencies will be partial
>> typelib
>> defined in orocos.toolchain
>> will be checked out in /usr/src/orocos-toolchain/typelib
>> git:git://gitorious.org//orocos-toolchain/typelib.git
>> branch=toolchain-2.2 NOT checked out yet, reported dependencies will be
>> partial
>> utilmm
>> defined in orocos.toolchain
>> will be checked out in /usr/src/orocos-toolchain/utilmm
>> git:git://gitorious.org//orocos-toolchain/utilmm.git
>> branch=toolchain-2.2 NOT checked out yet, reported dependencies will be
>> partial
>> utilrb
>> defined in orocos.toolchain
>> will be checked out in /usr/src/orocos-toolchain/utilrb
>> git:git://gitorious.org//orocos-toolchain/utilrb.git
>> branch=toolchain-2.2 NOT checked out yet, reported dependencies will be
>> partial
>>
>> WARN: the following packages are not yet checked out:
>> WARN: log4cpp, ocl, orogen, rtt
>> WARN: typelib, utilmm, utilrb
>> WARN: therefore, the package list above and the listed dependencies are
>> probably not complete
>>
>>
>> autoproj bootstrap successfully finished
>>
>> To further use autoproj and the installed software, you
>> must add the following line at the bottom of your .bashrc:
>> source /usr/src/orocos-toolchain/env.sh
>>
>> WARNING: autoproj will not work until your restart all
>> your consoles, or run the following in them:
>> $ source /usr/src/orocos-toolchain/env.sh
>>
>> To import and build the packages, you can now run
>> autoproj update
>> autoproj build
>>
>> The resulting software is installed in
>> /usr/src/orocos-toolchain/install
>>
>> Access method to gitorious (git, http or ssh): git
>> autodetecting the operating system
>> looking for RubyGems updates
>> updating autoproj main configuration
>> switching branch of autoproj_main_configuration to master
>> autoproj: updating remote definitions of package sets
>> updating orocos.toolchain
>>
>> autoproj: loading ...
>> run 'autoproj reconfigure' to change configuration options
>> and use 'autoproj switch-config' to change the remote source for
>> autoproj's main build configuration
>> the target operating system for Orocos/RTT (gnulinux or xenomai):
>> gnulinux which CORBA implementation should the RTT use ? omniorb
>>
>> autoproj: importing and loading selected packages
>> checking out log4cpp
>> checking out ocl
>> checking out orogen
>> checking out rtt
>> Build failed: rtt: failed in import phase
>> 'git clone -o autobuild git://gitorious.org//orocos-toolchain/rtt.git
>> /usr/src/orocos-toolchain/rtt' returned status 128 see
>> /usr/src/orocos-toolchain/install/log/rtt-import.log for details last 7
>> lines are:
>>
>> Mon Dec 13 17:36:23 +0100 2010: running
>> git clone -o autobuild
>> git://gitorious.org//orocos-toolchain/rtt.git
>> /usr/src/orocos-toolchain/rtt
>>
>> Initialized empty Git repository in /usr/src/orocos-toolchain/rtt/.git/
>> fatal: The remote end hung up unexpectedly
>> fatal: early EOF
>> fatal: index-pack failed
>
> This is a problem with gitorious. It's tempting to move back to github, since
> we never had issues there, and there doesn't pass a week without gitorious
> being down or broken.

I re-had the gitorious vs. github discussion with some of my colleagues.

* gitorious is open source. What it means -- and we actually do that
-- is that one can have an internal gitorious server for internal,
non-public, projects and an external one for the open-source stuff.
Not having two completely different environments is a great plus. And
not having to explain to management that, yes, it is *probably* fine
to have the code on the cloud is also a big plus. And I mean the
probably. Hacked servers happen all the time.
* it seems that when gitorious is "down", it is the git server that is
actually misbehaving. A colleague of mind told me that everytime it
failed, switching to http would do the trick. I'll implement a
fallback mechanism into autoproj to exploit this.

On 12/14/2010 10:07 AM, Peter Soetens wrote:
> On Monday 13 December 2010 19:06:17 gprizzi [..] ... wrote:
>> Dear sirs,
>>
>> I tried to install Toolchain 2.2. on Ubuntu using the following commands:
>>
>> mkdir orocos-toolchain
>> cd orocos-toolchain
>> wget
>> http://gitorious.com/orocos-toolchain/build/blobs/raw/toolchain-2.2/bootst
>> rap.sh sh bootstrap.sh
>>
>> but installation fails on Lua as you can see from the below error messages.
>>
>> What have I to do to complete installation?
>>
>> Thank you for your support.
>>
>> Gianpaolo Rizzi
>>
>>
>>
>> root@UBU1004:/usr/src/orocos-toolchain# wget
>> http://gitorious.com/orocos-toolchain/build/blobs/raw/toolchain-2.2/bootst
>> rap.sh --2010-12-13 17:28:53--
>> http://gitorious.com/orocos-toolchain/build/blobs/raw/toolchain-2.2/bootst
>> rap.sh Resolving gitorious.com... 87.238.52.168
>> Connecting to gitorious.com|87.238.52.168|:80... connected.
>> HTTP request sent, awaiting response... 200 OK
>> Cookie coming from gitorious.com attempted to set domain to gitorious.com
>> Length: 589 [application/sh]
>> Saving to: `bootstrap.sh'
>>
>> 100%[======================================================================
>> =========>] 589 --.-K/s in 0s
>>
>> 2010-12-13 17:28:54 (33.3 MB/s) - `bootstrap.sh' saved [589/589]
>>
>> root@UBU1004:/usr/src/orocos-toolchain# sn bootstrap.sh
>> The program 'sn' is currently not installed. You can install it by typing:
>> apt-get install mono-devel
>> root@UBU1004:/usr/src/orocos-toolchain# sh bootstrap.sh
>> --2010-12-13 17:29:13--
>> http://doudou.github.com/autoproj/autoproj_bootstrap Resolving
>> doudou.github.com... 207.97.227.245
>> Connecting to doudou.github.com|207.97.227.245|:80... connected.
>> HTTP request sent, awaiting response... 200 OK
>> Length: 52153 (51K) [application/octet-stream]
>> Saving to: `autoproj_bootstrap'
>>
>> 100%[======================================================================
>> =========>] 52,153 107K/s in 0.5s
>>
>> 2010-12-13 17:29:15 (107 KB/s) - `autoproj_bootstrap' saved [52153/52153]
>>
>> The current directory is not empty, continue bootstrapping anyway ? [yes]
>> autodetecting the operating system
>> Which prepackaged software (a.k.a. 'osdeps') should autoproj install
>> automatically (all, ruby, os, none) ? The software packages that autoproj
>> will have to build may require other prepackaged softwares (a.k.a. OS
>> dependencies) to be installed (RubyGems packages, packages from your
>> operating system/distribution, ...). Autoproj is able to install those
>> automatically for you.
>>
>> Advanced users may want to control this behaviour. Additionally, the
>> installation of some packages require administration rights, which you
>> may not have. This option is meant to allow you to control autoproj's
>> behaviour while handling OS dependencies.
>>
>> * if you say "all", it will install all packages automatically.
>> This requires root access thru 'sudo'
>> * if you say "ruby", only the Ruby packages will be installed.
>> Installing these packages does not require root access.
>> * if you say "os", only the OS-provided packages will be installed.
>> Installing these packages requires root access.
>> * if you say "none", autoproj will not do anything related to the
>> OS dependencies.
>>
>> As any configuration value, the mode can be changed anytime by calling
>> an autoproj operation with the --reconfigure option (e.g. autoproj
>> update --reconfigure).
>>
>> Finally, OS dependencies can be installed by calling "autoproj osdeps"
>> with the corresponding option (--all, --ruby, --os or --none). [all]
>> autoproj: installing a proper Ruby environment (this can take a long time)
>> autoproj: installing autoproj and its dependencies (this can take a long
>> time) installing/updating RubyGems dependencies: autobuild, rdoc
>> Enclosing class/module 'mUtilrb' for class WeakRef not known
>> Enclosing class/module 'cWeakRef' for class RefError not known
>> Enclosing class/module 'mUtilrb' for class WeakRef not known
>> Enclosing class/module 'cWeakRef' for class RefError not known
>> installing/updating RubyGems dependencies: autoproj
>> autodetecting the operating system
>> checking out autoproj main configuration
>> Access method to gitorious (git, http or ssh)
>> Use 'ssh' only if you have a gitorious account and have commit rights
>> on the Orocos projects. Otherwise, we advise you to use 'git' [git]
>> Which prepackaged software (a.k.a. 'osdeps') should autoproj install
>> automatically (all, ruby, os, none) ? all autoproj: updating remote
>> definitions of package sets
>> checking out git:git://gitorious.org//orocos-toolchain/autoproj.git
>> branch=toolchain-2.2
>>
>> autoproj: loading ...
>> run 'autoproj reconfigure' to change configuration options
>> and use 'autoproj switch-config' to change the remote source for
>> autoproj's main build configuration
>> the target operating system for Orocos/RTT (gnulinux or xenomai)
>> [gnulinux] which CORBA implementation should the RTT use ?
>> Answer 'none' to disable CORBA, otherwise pick either tao or omniorb
>> [omniorb]
>>
>> autoproj: package sets
>> orocos.toolchain (listed in manifest)
>> from: git:git://gitorious.org//orocos-toolchain/autoproj.git
>> branch=toolchain-2.2 local:
>> /usr/src/orocos-toolchain/autoproj/remotes/orocos.toolchain defines:
>> log4cpp, ocl, orogen, rtt, typelib, utilmm, utilrb
>>
>> autoproj: packages
>> log4cpp
>> defined in orocos.toolchain
>> will be checked out in /usr/src/orocos-toolchain/log4cpp
>> git:git://gitorious.org//orocos-toolchain/log4cpp.git
>> branch=toolchain-2.2 NOT checked out yet, reported dependencies will be
>> partial
>> ocl
>> defined in orocos.toolchain
>> will be checked out in /usr/src/orocos-toolchain/ocl
>> git:git://gitorious.org//orocos-toolchain/ocl.git branch=toolchain-2.2
>> NOT checked out yet, reported dependencies will be partial
>> orogen
>> defined in orocos.toolchain
>> will be checked out in /usr/src/orocos-toolchain/orogen
>> git:git://gitorious.org//orocos-toolchain/orogen.git
>> branch=toolchain-2.2 NOT checked out yet, reported dependencies will be
>> partial
>> rtt
>> defined in orocos.toolchain
>> will be checked out in /usr/src/orocos-toolchain/rtt
>> git:git://gitorious.org//orocos-toolchain/rtt.git branch=toolchain-2.2
>> NOT checked out yet, reported dependencies will be partial
>> typelib
>> defined in orocos.toolchain
>> will be checked out in /usr/src/orocos-toolchain/typelib
>> git:git://gitorious.org//orocos-toolchain/typelib.git
>> branch=toolchain-2.2 NOT checked out yet, reported dependencies will be
>> partial
>> utilmm
>> defined in orocos.toolchain
>> will be checked out in /usr/src/orocos-toolchain/utilmm
>> git:git://gitorious.org//orocos-toolchain/utilmm.git
>> branch=toolchain-2.2 NOT checked out yet, reported dependencies will be
>> partial
>> utilrb
>> defined in orocos.toolchain
>> will be checked out in /usr/src/orocos-toolchain/utilrb
>> git:git://gitorious.org//orocos-toolchain/utilrb.git
>> branch=toolchain-2.2 NOT checked out yet, reported dependencies will be
>> partial
>>
>> WARN: the following packages are not yet checked out:
>> WARN: log4cpp, ocl, orogen, rtt
>> WARN: typelib, utilmm, utilrb
>> WARN: therefore, the package list above and the listed dependencies are
>> probably not complete
>>
>>
>> autoproj bootstrap successfully finished
>>
>> To further use autoproj and the installed software, you
>> must add the following line at the bottom of your .bashrc:
>> source /usr/src/orocos-toolchain/env.sh
>>
>> WARNING: autoproj will not work until your restart all
>> your consoles, or run the following in them:
>> $ source /usr/src/orocos-toolchain/env.sh
>>
>> To import and build the packages, you can now run
>> autoproj update
>> autoproj build
>>
>> The resulting software is installed in
>> /usr/src/orocos-toolchain/install
>>
>> Access method to gitorious (git, http or ssh): git
>> autodetecting the operating system
>> looking for RubyGems updates
>> updating autoproj main configuration
>> switching branch of autoproj_main_configuration to master
>> autoproj: updating remote definitions of package sets
>> updating orocos.toolchain
>>
>> autoproj: loading ...
>> run 'autoproj reconfigure' to change configuration options
>> and use 'autoproj switch-config' to change the remote source for
>> autoproj's main build configuration
>> the target operating system for Orocos/RTT (gnulinux or xenomai):
>> gnulinux which CORBA implementation should the RTT use ? omniorb
>>
>> autoproj: importing and loading selected packages
>> checking out log4cpp
>> checking out ocl
>> checking out orogen
>> checking out rtt
>> Build failed: rtt: failed in import phase
>> 'git clone -o autobuild git://gitorious.org//orocos-toolchain/rtt.git
>> /usr/src/orocos-toolchain/rtt' returned status 128 see
>> /usr/src/orocos-toolchain/install/log/rtt-import.log for details last 7
>> lines are:
>>
>> Mon Dec 13 17:36:23 +0100 2010: running
>> git clone -o autobuild
>> git://gitorious.org//orocos-toolchain/rtt.git
>> /usr/src/orocos-toolchain/rtt
>>
>> Initialized empty Git repository in /usr/src/orocos-toolchain/rtt/.git/
>> fatal: The remote end hung up unexpectedly
>> fatal: early EOF
>> fatal: index-pack failed
>
> This is a problem with gitorious. It's tempting to move back to github, since
> we never had issues there, and there doesn't pass a week without gitorious
> being down or broken.
*Bing* I actually had the same issues with github.

But I agree, it is indeed annoying.

On 12/14/2010 10:05 AM, Peter Soetens wrote:
> On Monday 13 December 2010 19:06:17 gprizzi [..] ... wrote:
>> Dear sirs,
>>
>> I tried to install Toolchain 2.2. on Ubuntu using the following commands:
>>
>> mkdir orocos-toolchain
>> cd orocos-toolchain
>> wget
>> http://gitorious.com/orocos-toolchain/build/blobs/raw/toolchain-2.2/bootst
>> rap.sh sh bootstrap.sh
>
> Sylvain, is there a way to make bootstrap non-interactive such that we can
> include running this in our automated builds ?

Yes. I'm cleaning up our build server scripts and I'll send it to you.
--
Sylvain Joyeux (Dr. Ing.)
Researcher - Space and Security Robotics
DFKI Robotics Innovation Center
Bremen, Robert-Hooke-Straße 5, 28359 Bremen, Germany

Phone: +49 421 218-64136
Fax: +49 421 218-64150
Email: sylvain [dot] joyeux [..] ...

Weitere Informationen: http://www.dfki.de
--
Orocos-Dev mailing list
Orocos-Dev [..] ...
http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev

Should not this be automatically done by the toolchain ? Has it been
forgotten ? Or is this a normal installation describe somewhere else in a
Readme or kind of ?

2010/12/13 Ruben Smits <ruben [dot] smits [..] ...>

> On Monday 13 December 2010 19:06:17 gprizzi [..] ... wrote:
> > Dear sirs,
> >
> > I tried to install Toolchain 2.2. on Ubuntu using the following commands:
> >
> >
> > mkdir orocos-toolchain
> > cd orocos-toolchain
> > wget
> >
> http://gitorious.com/orocos-toolchain/build/blobs/raw/toolchain-2.2/bootst
> > rap.sh sh bootstrap.sh
> >
> > but installation fails on Lua as you can see from the below error
> messages.
> >
> > What have I to do to complete installation?
>
> On debian-like systems you need the package liblua5.1-0-dev:
>
> apt-get install liblua5.1-0-dev
>
> Ruben
>
> > Thank you for your support.
> >
> > Gianpaolo Rizzi
> >
> >
> >
> > root@UBU1004:/usr/src/orocos-toolchain# wget
> >
> http://gitorious.com/orocos-toolchain/build/blobs/raw/toolchain-2.2/bootst
> > rap.sh --2010-12-13 17:28:53--
> >
> http://gitorious.com/orocos-toolchain/build/blobs/raw/toolchain-2.2/bootst
> > rap.sh Resolving gitorious.com... 87.238.52.168
> > Connecting to gitorious.com|87.238.52.168|:80... connected.
> > HTTP request sent, awaiting response... 200 OK
> > Cookie coming from gitorious.com attempted to set domain to
> gitorious.com
> > Length: 589 [application/sh]
> > Saving to: `bootstrap.sh'
> >
> >
> 100%[======================================================================
> > =========>] 589 --.-K/s in 0s
> >
> > 2010-12-13 17:28:54 (33.3 MB/s) - `bootstrap.sh' saved [589/589]
> >
> > root@UBU1004:/usr/src/orocos-toolchain# sn bootstrap.sh
> > The program 'sn' is currently not installed. You can install it by
> typing:
> > apt-get install mono-devel
> > root@UBU1004:/usr/src/orocos-toolchain# sh bootstrap.sh
> > --2010-12-13 17:29:13--
> > http://doudou.github.com/autoproj/autoproj_bootstrap Resolving
> > doudou.github.com... 207.97.227.245
> > Connecting to doudou.github.com|207.97.227.245|:80... connected.
> > HTTP request sent, awaiting response... 200 OK
> > Length: 52153 (51K) [application/octet-stream]
> > Saving to: `autoproj_bootstrap'
> >
> >
> 100%[======================================================================
> > =========>] 52,153 107K/s in 0.5s
> >
> > 2010-12-13 17:29:15 (107 KB/s) - `autoproj_bootstrap' saved [52153/52153]
> >
> > The current directory is not empty, continue bootstrapping anyway ? [yes]
> > autodetecting the operating system
> > Which prepackaged software (a.k.a. 'osdeps') should autoproj install
> > automatically (all, ruby, os, none) ? The software packages that autoproj
> > will have to build may require other prepackaged softwares (a.k.a. OS
> > dependencies) to be installed (RubyGems packages, packages from your
> > operating system/distribution, ...). Autoproj is able to install those
> > automatically for you.
> >
> > Advanced users may want to control this behaviour. Additionally, the
> > installation of some packages require administration rights, which
> you
> > may not have. This option is meant to allow you to control autoproj's
> > behaviour while handling OS dependencies.
> >
> > * if you say "all", it will install all packages automatically.
> > This requires root access thru 'sudo'
> > * if you say "ruby", only the Ruby packages will be installed.
> > Installing these packages does not require root access.
> > * if you say "os", only the OS-provided packages will be installed.
> > Installing these packages requires root access.
> > * if you say "none", autoproj will not do anything related to the
> > OS dependencies.
> >
> > As any configuration value, the mode can be changed anytime by
> calling
> > an autoproj operation with the --reconfigure option (e.g. autoproj
> > update --reconfigure).
> >
> > Finally, OS dependencies can be installed by calling "autoproj
> osdeps"
> > with the corresponding option (--all, --ruby, --os or --none). [all]
> > autoproj: installing a proper Ruby environment (this can take a long
> time)
> > autoproj: installing autoproj and its dependencies (this can take a long
> > time) installing/updating RubyGems dependencies: autobuild, rdoc
> > Enclosing class/module 'mUtilrb' for class WeakRef not known
> > Enclosing class/module 'cWeakRef' for class RefError not known
> > Enclosing class/module 'mUtilrb' for class WeakRef not known
> > Enclosing class/module 'cWeakRef' for class RefError not known
> > installing/updating RubyGems dependencies: autoproj
> > autodetecting the operating system
> > checking out autoproj main configuration
> > Access method to gitorious (git, http or ssh)
> > Use 'ssh' only if you have a gitorious account and have commit rights
> > on the Orocos projects. Otherwise, we advise you to use 'git' [git]
> > Which prepackaged software (a.k.a. 'osdeps') should autoproj install
> > automatically (all, ruby, os, none) ? all autoproj: updating remote
> > definitions of package sets
> > checking out git:git://gitorious.org//orocos-toolchain/autoproj.git
> > branch=toolchain-2.2
> >
> > autoproj: loading ...
> > run 'autoproj reconfigure' to change configuration options
> > and use 'autoproj switch-config' to change the remote source for
> > autoproj's main build configuration
> > the target operating system for Orocos/RTT (gnulinux or xenomai)
> > [gnulinux] which CORBA implementation should the RTT use ?
> > Answer 'none' to disable CORBA, otherwise pick either tao or omniorb
> > [omniorb]
> >
> > autoproj: package sets
> > orocos.toolchain (listed in manifest)
> > from: git:git://gitorious.org//orocos-toolchain/autoproj.git
> > branch=toolchain-2.2 local:
> > /usr/src/orocos-toolchain/autoproj/remotes/orocos.toolchain defines:
> > log4cpp, ocl, orogen, rtt, typelib, utilmm, utilrb
> >
> > autoproj: packages
> > log4cpp
> > defined in orocos.toolchain
> > will be checked out in /usr/src/orocos-toolchain/log4cpp
> > git:git://gitorious.org//orocos-toolchain/log4cpp.git
> > branch=toolchain-2.2 NOT checked out yet, reported dependencies will be
> > partial
> > ocl
> > defined in orocos.toolchain
> > will be checked out in /usr/src/orocos-toolchain/ocl
> > git:git://gitorious.org//orocos-toolchain/ocl.gitbranch=toolchain-2.2
> > NOT checked out yet, reported dependencies will be partial
> > orogen
> > defined in orocos.toolchain
> > will be checked out in /usr/src/orocos-toolchain/orogen
> > git:git://gitorious.org//orocos-toolchain/orogen.git
> > branch=toolchain-2.2 NOT checked out yet, reported dependencies will be
> > partial
> > rtt
> > defined in orocos.toolchain
> > will be checked out in /usr/src/orocos-toolchain/rtt
> > git:git://gitorious.org//orocos-toolchain/rtt.gitbranch=toolchain-2.2
> > NOT checked out yet, reported dependencies will be partial
> > typelib
> > defined in orocos.toolchain
> > will be checked out in /usr/src/orocos-toolchain/typelib
> > git:git://gitorious.org//orocos-toolchain/typelib.git
> > branch=toolchain-2.2 NOT checked out yet, reported dependencies will be
> > partial
> > utilmm
> > defined in orocos.toolchain
> > will be checked out in /usr/src/orocos-toolchain/utilmm
> > git:git://gitorious.org//orocos-toolchain/utilmm.git
> > branch=toolchain-2.2 NOT checked out yet, reported dependencies will be
> > partial
> > utilrb
> > defined in orocos.toolchain
> > will be checked out in /usr/src/orocos-toolchain/utilrb
> > git:git://gitorious.org//orocos-toolchain/utilrb.git
> > branch=toolchain-2.2 NOT checked out yet, reported dependencies will be
> > partial
> >
> > WARN: the following packages are not yet checked out:
> > WARN: log4cpp, ocl, orogen, rtt
> > WARN: typelib, utilmm, utilrb
> > WARN: therefore, the package list above and the listed dependencies are
> > probably not complete
> >
> >
> > autoproj bootstrap successfully finished
> >
> > To further use autoproj and the installed software, you
> > must add the following line at the bottom of your .bashrc:
> > source /usr/src/orocos-toolchain/env.sh
> >
> > WARNING: autoproj will not work until your restart all
> > your consoles, or run the following in them:
> > $ source /usr/src/orocos-toolchain/env.sh
> >
> > To import and build the packages, you can now run
> > autoproj update
> > autoproj build
> >
> > The resulting software is installed in
> > /usr/src/orocos-toolchain/install
> >
> > Access method to gitorious (git, http or ssh): git
> > autodetecting the operating system
> > looking for RubyGems updates
> > updating autoproj main configuration
> > switching branch of autoproj_main_configuration to master
> > autoproj: updating remote definitions of package sets
> > updating orocos.toolchain
> >
> > autoproj: loading ...
> > run 'autoproj reconfigure' to change configuration options
> > and use 'autoproj switch-config' to change the remote source for
> > autoproj's main build configuration
> > the target operating system for Orocos/RTT (gnulinux or xenomai):
> > gnulinux which CORBA implementation should the RTT use ? omniorb
> >
> > autoproj: importing and loading selected packages
> > checking out log4cpp
> > checking out ocl
> > checking out orogen
> > checking out rtt
> > Build failed: rtt: failed in import phase
> > 'git clone -o autobuild git://
> gitorious.org//orocos-toolchain/rtt.git
> > /usr/src/orocos-toolchain/rtt' returned status 128 see
> > /usr/src/orocos-toolchain/install/log/rtt-import.log for details last 7
> > lines are:
> >
> > Mon Dec 13 17:36:23 +0100 2010: running
> > git clone -o autobuild
> > git://gitorious.org//orocos-toolchain/rtt.git
> > /usr/src/orocos-toolchain/rtt
> >
> > Initialized empty Git repository in
> /usr/src/orocos-toolchain/rtt/.git/
> > fatal: The remote end hung up unexpectedly
> > fatal: early EOF
> > fatal: index-pack failed
> > Access method to gitorious (git, http or ssh): git
> > Which prepackaged software (a.k.a. 'osdeps') should autoproj install
> > automatically (all, ruby, os, none) ? all
> >
> > autoproj: loading ...
> > run 'autoproj reconfigure' to change configuration options
> > and use 'autoproj switch-config' to change the remote source for
> > autoproj's main build configuration
> > the target operating system for Orocos/RTT (gnulinux or xenomai):
> > gnulinux which CORBA implementation should the RTT use ? omniorb
> >
> > autoproj: importing and loading selected packages
> > checking out rtt
> > checking out typelib
> > checking out utilmm
> > checking out utilrb
> > autoproj: building and installing packages
> > configuring build system for log4cpp
> > building log4cpp [progress not available]
> > installing log4cpp
> > generating and configuring build system for utilmm
> > building utilmm (100%)
> > installing utilmm
> > generating and configuring build system for rtt
> > building rtt (100%)
> > installing rtt
> > generating and configuring build system for ocl
> > Build failed: ocl: failed in configure phase
> > 'cmake -DCMAKE_INSTALL_PREFIX=/usr/src/orocos-toolchain/install
> > -DOROCOS_TARGET=gnulinux /usr/src/orocos-toolchain/ocl' returned status 1
> > see /usr/src/orocos-toolchain/install/log/ocl-configure.log for details
> > last 10 lines are:
> >
> > Building library orocos-deployment
> > Building library orocos-deployment-corba
> > CMake Error at
> > /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:70
> > (MESSAGE): Could NOT find Lua51 (missing: LUA_LIBRARIES LUA_INCLUDE_DIR)
> > Call Stack (most recent call first):
> > /usr/share/cmake-2.8/Modules/FindLua51.cmake:72
> > (FIND_PACKAGE_HANDLE_STANDARD_ARGS) lua/CMakeLists.txt:7 (find_package)
> >
> >
> > -- Configuring incomplete, errors occurred!
> > root@UBU1004:/usr/src/orocos-toolchain#
> --
> Orocos-Dev mailing list
> Orocos-Dev [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev
>