Orocos ToolChain2.2 error on Lua

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/boot...
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/boot...
--2010-12-13 17:28:53-- http://gitorious.com/orocos-toolchain/build/blobs/raw/toolchain-2.2/boot...
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
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 ToolChain2.2 error on Lua

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

Orocos ToolChain2.2 error on Lua

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.

Orocos ToolChain2.2 error on Lua

I tried a new installation from zero and something seems to be wrong with
boostrap :
manifest /opt/orocos2/ocl/manifest.xml of ocl from orocos.toolchain lists
'lua-dev' as dependency, but it is neither a normal package nor an osdeps
package. osdeps reports: there is no osdeps definition for lua-dev
ard@ard-host-4:/opt/orocos2$

complete log :

ard@ard-host-4:/opt/orocos2$ wget
http://gitorious.com/orocos-toolchain/build/blobs/raw/toolchain-2.2/boot...
--2010-12-16 01:24:05--
http://gitorious.com/orocos-toolchain/build/blobs/raw/toolchain-2.2/boot...
Résolution de gitorious.com... 87.238.52.168
Connexion vers gitorious.com|87.238.52.168|:80...connecté.
requête HTTP transmise, en attente de la réponse...200 OK
Un cookie provenant de gitorious.com a tenté de changer le domaine en
gitorious.com
Longueur: 589 [application/sh]
Sauvegarde en : «bootstrap.sh»

100%[=========================================================================================================================================================================================>]
589 --.-K/s ds 0s

2010-12-16 01:24:07 (42,8 MB/s) - «bootstrap.sh» sauvegardé [589/589]

ard@ard-host-4:/opt/orocos2$ sh bootstrap.sh
--2010-12-16 01:24:10--
http://doudou.github.com/autoproj/autoproj_bootstrap
Résolution de doudou.github.com... 207.97.227.245
Connexion vers doudou.github.com|207.97.227.245|:80...connecté.
requête HTTP transmise, en attente de la réponse...200 OK
Longueur: 52153 (51K) [application/octet-stream]
Sauvegarde en : «autoproj_bootstrap»

100%[=========================================================================================================================================================================================>]
52 153 95,8K/s ds 0,5s

2010-12-16 01:24:11 (95,8 KB/s) - «autoproj_bootstrap» sauvegardé
[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)
installing OS packages: libopenssl-ruby1.8
autoproj: installing autoproj and its dependencies (this can take a long
time)
looking for RubyGems updates
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: 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.gitbranch=toolchain-2.2
local:
/opt/orocos2/.remotes/git_git___gitorious_org__orocos_toolchain_autoproj_git_branch_toolchain_2_2
defines: log4cpp, ocl, orogen, rtt, typelib, utilmm, utilrb

autoproj: packages
log4cpp
defined in orocos.toolchain
will be checked out in /opt/orocos2/log4cpp
git:git://gitorious.org//orocos-toolchain/log4cpp.gitbranch=toolchain-2.2
NOT checked out yet, reported dependencies will be partial
ocl
defined in orocos.toolchain
will be checked out in /opt/orocos2/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 /opt/orocos2/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 /opt/orocos2/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 /opt/orocos2/typelib
git:git://gitorious.org//orocos-toolchain/typelib.gitbranch=toolchain-2.2
NOT checked out yet, reported dependencies will be partial
utilmm
defined in orocos.toolchain
will be checked out in /opt/orocos2/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 /opt/orocos2/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 /opt/orocos2/env.sh

WARNING: autoproj will not work until your restart all
your consoles, or run the following in them:
$ source /opt/orocos2/env.sh

To import and build the packages, you can now run
autoproj update
autoproj build

The resulting software is installed in
/opt/orocos2/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

manifest /opt/orocos2/ocl/manifest.xml of ocl from orocos.toolchain lists
'lua-dev' as dependency, but it is neither a normal package nor an osdeps
package. osdeps reports: there is no osdeps definition for lua-dev
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

manifest /opt/orocos2/ocl/manifest.xml of ocl from orocos.toolchain lists
'lua-dev' as dependency, but it is neither a normal package nor an osdeps
package. osdeps reports: there is no osdeps definition for lua-dev
ard@ard-host-4:/opt/orocos2$

2010/12/14 Sylvain Joyeux <sylvain [dot] joyeux [..] ...>

> 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.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
> >
> > 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.
>
> --
> 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
>

Orocos ToolChain2.2 error on Lua

On Thursday 16 December 2010 01:30:35 Willy Lambert wrote:
> I tried a new installation from zero and something seems to be wrong with
> boostrap :
> manifest /opt/orocos2/ocl/manifest.xml of ocl from orocos.toolchain lists
> 'lua-dev' as dependency, but it is neither a normal package nor an osdeps
> package. osdeps reports: there is no osdeps definition for lua-dev
> ard@ard-host-4:/opt/orocos2$

Aargh. Try again please. I overlooked one merge request.

Peter

Orocos ToolChain2.2 error on Lua

On Thu, Dec 16, 2010 at 09:10:57AM +0100, Peter Soetens wrote:
> On Thursday 16 December 2010 01:30:35 Willy Lambert wrote:
> > I tried a new installation from zero and something seems to be wrong with
> > boostrap :
> > manifest /opt/orocos2/ocl/manifest.xml of ocl from orocos.toolchain lists
> > 'lua-dev' as dependency, but it is neither a normal package nor an osdeps
> > package. osdeps reports: there is no osdeps definition for lua-dev
> > ard@ard-host-4:/opt/orocos2$
>
> Aargh. Try again please. I overlooked one merge request.

I guess its my fault for pushing the autoproj fixes to master and not
toolchain-2.2, right?

Markus

Orocos ToolChain2.2 error on Lua

On Thursday 16 December 2010 09:15:26 Markus Klotzbuecher wrote:
> On Thu, Dec 16, 2010 at 09:10:57AM +0100, Peter Soetens wrote:
> > On Thursday 16 December 2010 01:30:35 Willy Lambert wrote:
> > > I tried a new installation from zero and something seems to be wrong
> > > with boostrap :
> > > manifest /opt/orocos2/ocl/manifest.xml of ocl from orocos.toolchain
> > > lists 'lua-dev' as dependency, but it is neither a normal package nor
> > > an osdeps package. osdeps reports: there is no osdeps definition for
> > > lua-dev ard@ard-host-4:/opt/orocos2$
> >
> > Aargh. Try again please. I overlooked one merge request.
>
> I guess its my fault for pushing the autoproj fixes to master and not
> toolchain-2.2, right?

I merged them on toolchain-2.2 anyway (I always merge from release branch to
master).

I knew there were 3 merges to do, and I overlooked one...

Peter

Orocos ToolChain2.2 error on Lua

seems still bad, did I went wrong in my procedure ?

ard@ard-host-4:/opt/orocos2$ sudo rm * -r
rm: impossible de supprimer « * »: Aucun fichier ou dossier de ce type
ard@ard-host-4:/opt/orocos2$ wget
http://gitorious.com/orocos-toolchain/build/blobs/raw/toolchain-2.2/boot...
--2010-12-16 10:22:55--
http://gitorious.com/orocos-toolchain/build/blobs/raw/toolchain-2.2/boot...
Résolution de gitorious.com... 87.238.52.168
Connexion vers gitorious.com|87.238.52.168|:80...connecté.
requête HTTP transmise, en attente de la réponse...200 OK
Un cookie provenant de gitorious.com a tenté de changer le domaine en
gitorious.com
Longueur: 589 [application/sh]
Sauvegarde en : «bootstrap.sh»

100%[===========================================================================================================================>]
589 --.-K/s ds 0s

2010-12-16 10:22:55 (37,9 MB/s) - «bootstrap.sh» sauvegardé [589/589]

ard@ard-host-4:/opt/orocos2$ sh bootstrap.sh
--2010-12-16 10:23:01--
http://doudou.github.com/autoproj/autoproj_bootstrap
Résolution de doudou.github.com... 207.97.227.245
Connexion vers doudou.github.com|207.97.227.245|:80...connecté.
requête HTTP transmise, en attente de la réponse...200 OK
Longueur: 52153 (51K) [application/octet-stream]
Sauvegarde en : «autoproj_bootstrap»

100%[===========================================================================================================================>]
52 153 90,8K/s ds 0,6s

2010-12-16 10:23:03 (90,8 KB/s) - «autoproj_bootstrap» sauvegardé
[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)
installing OS packages: libopenssl-ruby1.8
autoproj: installing autoproj and its dependencies (this can take a long
time)
looking for RubyGems updates
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: 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.gitbranch=toolchain-2.2
local:
/opt/orocos2/.remotes/git_git___gitorious_org__orocos_toolchain_autoproj_git_branch_toolchain_2_2
defines: log4cpp, ocl, orogen, rtt, typelib, utilmm, utilrb

autoproj: packages
log4cpp
defined in orocos.toolchain
will be checked out in /opt/orocos2/log4cpp
git:git://gitorious.org//orocos-toolchain/log4cpp.gitbranch=toolchain-2.2
NOT checked out yet, reported dependencies will be partial
ocl
defined in orocos.toolchain
will be checked out in /opt/orocos2/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 /opt/orocos2/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 /opt/orocos2/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 /opt/orocos2/typelib
git:git://gitorious.org//orocos-toolchain/typelib.gitbranch=toolchain-2.2
NOT checked out yet, reported dependencies will be partial
utilmm
defined in orocos.toolchain
will be checked out in /opt/orocos2/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 /opt/orocos2/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 /opt/orocos2/env.sh

WARNING: autoproj will not work until your restart all
your consoles, or run the following in them:
$ source /opt/orocos2/env.sh

To import and build the packages, you can now run
autoproj update
autoproj build

The resulting software is installed in
/opt/orocos2/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
checking out typelib
checking out utilmm
checking out utilrb
installing OS packages: liblua5.1-0-dev, libreadline-dev

autodetected the shell to be bash, sourcing autoproj shell helpers
add "Autoproj.shell_helpers = false" in autoproj/init.rb to disable
autoproj: updated /opt/orocos2/env.sh
Build finished successfully at Thu Dec 16 10:24:09 +0100 2010
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
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=/opt/orocos2/install
-DOROCOS_TARGET=gnulinux /opt/orocos2/ocl' returned status 1
see /opt/orocos2/install/log/ocl-configure.log for details
last 10 lines are:

cmake_policy command to set the policy and suppress this warning.
This warning is for project developers. Use -Wno-dev to suppress it.

Building component orocos-logging in library orocos-logging-gnulinux
Building library orocos-log4cpp
-- Found Lua51: /usr/lib/liblua5.1.so;/usr/lib/libm.so
Building component orocos-lua in library orocos-lua-gnulinux
Building plugin library rttlua-plugin
Selected Libraries:
-- Configuring incomplete, errors occurred!
ard@ard-host-4:/opt/orocos2$

2010/12/16 Peter Soetens <peter [..] ...>

> On Thursday 16 December 2010 09:15:26 Markus Klotzbuecher wrote:
> > On Thu, Dec 16, 2010 at 09:10:57AM +0100, Peter Soetens wrote:
> > > On Thursday 16 December 2010 01:30:35 Willy Lambert wrote:
> > > > I tried a new installation from zero and something seems to be wrong
> > > > with boostrap :
> > > > manifest /opt/orocos2/ocl/manifest.xml of ocl from orocos.toolchain
> > > > lists 'lua-dev' as dependency, but it is neither a normal package nor
> > > > an osdeps package. osdeps reports: there is no osdeps definition for
> > > > lua-dev ard@ard-host-4:/opt/orocos2$
> > >
> > > Aargh. Try again please. I overlooked one merge request.
> >
> > I guess its my fault for pushing the autoproj fixes to master and not
> > toolchain-2.2, right?
>
> I merged them on toolchain-2.2 anyway (I always merge from release branch
> to
> master).
>
> I knew there were 3 merges to do, and I overlooked one...
>
> Peter
>

Orocos ToolChain2.2 error on Lua

On Thursday 16 December 2010 10:44:57 Willy Lambert wrote:
> seems still bad, did I went wrong in my procedure ?
...
> autoproj: importing and loading selected packages
> 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=/opt/orocos2/install
> -DOROCOS_TARGET=gnulinux /opt/orocos2/ocl' returned status 1
> see /opt/orocos2/install/log/ocl-configure.log for details
> last 10 lines are:
>
> cmake_policy command to set the policy and suppress this warning.
> This warning is for project developers. Use -Wno-dev to suppress it.
>
> Building component orocos-logging in library orocos-logging-gnulinux
> Building library orocos-log4cpp
> -- Found Lua51: /usr/lib/liblua5.1.so;/usr/lib/libm.so
> Building component orocos-lua in library orocos-lua-gnulinux
> Building plugin library rttlua-plugin
> Selected Libraries:
> -- Configuring incomplete, errors occurred!

I need to see your /opt/orocos2/install/log/ocl-configure.log file. I just fixed
a problem regarding detection of log4cpp installs, which is likely that you
hit too.

I have a successful build now. Maybe your luck will change this time ? :-]

Peter

Orocos ToolChain2.2 error on Lua

2010/12/16 Peter Soetens <peter [..] ...>

> On Thursday 16 December 2010 10:44:57 Willy Lambert wrote:
> > seems still bad, did I went wrong in my procedure ?
> ...
> > autoproj: importing and loading selected packages
> > 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=/opt/orocos2/install
> > -DOROCOS_TARGET=gnulinux /opt/orocos2/ocl' returned status 1
> > see /opt/orocos2/install/log/ocl-configure.log for details
> > last 10 lines are:
> >
> > cmake_policy command to set the policy and suppress this warning.
> > This warning is for project developers. Use -Wno-dev to suppress it.
> >
> > Building component orocos-logging in library orocos-logging-gnulinux
> > Building library orocos-log4cpp
> > -- Found Lua51: /usr/lib/liblua5.1.so;/usr/lib/libm.so
> > Building component orocos-lua in library orocos-lua-gnulinux
> > Building plugin library rttlua-plugin
> > Selected Libraries:
> > -- Configuring incomplete, errors occurred!
>
> I need to see your /opt/orocos2/install/log/ocl-configure.log file. I just
> fixed
> a problem regarding detection of log4cpp installs, which is likely that you
> hit too.
>
ard@ard-host-4:/opt/orocos2/install/log$ cat ocl-configure.log
Thu Dec 16 10:51:15 +0100 2010: running
cmake -DCMAKE_INSTALL_PREFIX=/opt/orocos2/install
-DOROCOS_TARGET=gnulinux /opt/orocos2/ocl

-- The C compiler identification is GNU
-- The CXX compiler identification is GNU
-- Check for working C compiler: /usr/bin/gcc
-- Check for working C compiler: /usr/bin/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
Orocos Component Library version (2.2.0)
No orocos-ocl.cmake file loaded, using default settings.See
orocos-ocl.default.cmake
Orocos-RTT found in
/opt/orocos2/install/lib/cmake/orocos-rtt/orocos-rtt-gnulinux-libraries.cmake
-- Found orocos-rtt 2.2.0 for the gnulinux target. Available transports:
corba mqueue
-- - Found requested orocos-rtt components: rtt-scripting rtt-marshalling
Looking for netcdf in /opt/orocos2/install
Can't find NETCDF
-- Found Doxygen: /usr/bin/doxygen
Found Doxygen -- documentation can be built
-- Found Curses: /usr/lib/libcurses.so
-- Looking for libncurses - found
-- Looking for readline/readline.h - found
-- Boost version: 1.42.0
-- Found the following Boost libraries:
-- program_options
-- filesystem
-- system
Building component orocos-ocl-common in library orocos-ocl-common-gnulinux
Building typekit library ocl
Building plugin library print
Building plugin library os
-- Found RTT_PLUGIN_rtt-scripting
Building library orocos-taskbrowser
Building component orocos-timer in library orocos-timer-gnulinux
Building component orocos-helloworld in library orocos-helloworld-gnulinux
-- Found RTT_PLUGIN_rtt-marshalling
Building component orocos-reporting in library orocos-reporting-gnulinux
-- Found RTT_PLUGIN_rtt-marshalling
-- Found RTT_PLUGIN_rtt-scripting
Building library orocos-deployment
Building library orocos-deployment-corba
CMake Error at logging/CMakeLists.txt:5 (message):
Can't build real-time logging service since log4cpp was not found.

CMake Error at logging/CMakeLists.txt:13 (INCLUDE_DIRECTORIES):
include_directories given empty-string as include directory.

CMake Warning (dev) at logging/CMakeLists.txt:14 (LINK_DIRECTORIES):
This command specifies the relative path

as a link directory.

Policy CMP0015 is not set: link_directories() treats paths relative to the
source dir. Run "cmake --help-policy CMP0015" for policy details. Use
the
cmake_policy command to set the policy and suppress this warning.
This warning is for project developers. Use -Wno-dev to suppress it.

Building component orocos-logging in library orocos-logging-gnulinux
Building library orocos-log4cpp
-- Found Lua51: /usr/lib/liblua5.1.so;/usr/lib/libm.so
Building component orocos-lua in library orocos-lua-gnulinux
Building plugin library rttlua-plugin
Selected Libraries:
-- Configuring incomplete, errors occurred!
ard@ard-host-4:/opt/orocos2/install/log$

> I have a successful build now. Maybe your luck will change this time ? :-]
>

I'll try again.

>
> Peter
>
>
>

Orocos ToolChain2.2 error on Lua

2010/12/16 Willy Lambert <lambert [dot] willy [..] ...>

>
>
> 2010/12/16 Peter Soetens <peter [..] ...>
>
>> On Thursday 16 December 2010 10:44:57 Willy Lambert wrote:
>>
>> > seems still bad, did I went wrong in my procedure ?
>> ...
>> > autoproj: importing and loading selected packages
>> > 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=/opt/orocos2/install
>> > -DOROCOS_TARGET=gnulinux /opt/orocos2/ocl' returned status 1
>> > see /opt/orocos2/install/log/ocl-configure.log for details
>> > last 10 lines are:
>> >
>> > cmake_policy command to set the policy and suppress this warning.
>> > This warning is for project developers. Use -Wno-dev to suppress
>> it.
>> >
>> > Building component orocos-logging in library orocos-logging-gnulinux
>> > Building library orocos-log4cpp
>> > -- Found Lua51: /usr/lib/liblua5.1.so;/usr/lib/libm.so
>> > Building component orocos-lua in library orocos-lua-gnulinux
>> > Building plugin library rttlua-plugin
>> > Selected Libraries:
>> > -- Configuring incomplete, errors occurred!
>>
>> I need to see your /opt/orocos2/install/log/ocl-configure.log file. I just
>> fixed
>> a problem regarding detection of log4cpp installs, which is likely that
>> you
>> hit too.
>>
> ard@ard-host-4:/opt/orocos2/install/log$ cat ocl-configure.log
> Thu Dec 16 10:51:15 +0100 2010: running
>
> cmake -DCMAKE_INSTALL_PREFIX=/opt/orocos2/install
> -DOROCOS_TARGET=gnulinux /opt/orocos2/ocl
>
> -- The C compiler identification is GNU
> -- The CXX compiler identification is GNU
> -- Check for working C compiler: /usr/bin/gcc
> -- Check for working C compiler: /usr/bin/gcc -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Check for working CXX compiler: /usr/bin/c++
> -- Check for working CXX compiler: /usr/bin/c++ -- works
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> Orocos Component Library version (2.2.0)
> No orocos-ocl.cmake file loaded, using default settings.See
> orocos-ocl.default.cmake
> Orocos-RTT found in
> /opt/orocos2/install/lib/cmake/orocos-rtt/orocos-rtt-gnulinux-libraries.cmake
> -- Found orocos-rtt 2.2.0 for the gnulinux target. Available transports:
> corba mqueue
> -- - Found requested orocos-rtt components: rtt-scripting rtt-marshalling
> Looking for netcdf in /opt/orocos2/install
> Can't find NETCDF
> -- Found Doxygen: /usr/bin/doxygen
> Found Doxygen -- documentation can be built
> -- Found Curses: /usr/lib/libcurses.so
> -- Looking for libncurses - found
> -- Looking for readline/readline.h - found
> -- Boost version: 1.42.0
> -- Found the following Boost libraries:
> -- program_options
> -- filesystem
> -- system
> Building component orocos-ocl-common in library orocos-ocl-common-gnulinux
> Building typekit library ocl
> Building plugin library print
> Building plugin library os
> -- Found RTT_PLUGIN_rtt-scripting
> Building library orocos-taskbrowser
> Building component orocos-timer in library orocos-timer-gnulinux
> Building component orocos-helloworld in library orocos-helloworld-gnulinux
> -- Found RTT_PLUGIN_rtt-marshalling
> Building component orocos-reporting in library orocos-reporting-gnulinux
> -- Found RTT_PLUGIN_rtt-marshalling
> -- Found RTT_PLUGIN_rtt-scripting
> Building library orocos-deployment
> Building library orocos-deployment-corba
> CMake Error at logging/CMakeLists.txt:5 (message):
> Can't build real-time logging service since log4cpp was not found.
>
>
> CMake Error at logging/CMakeLists.txt:13 (INCLUDE_DIRECTORIES):
> include_directories given empty-string as include directory.
>
>
> CMake Warning (dev) at logging/CMakeLists.txt:14 (LINK_DIRECTORIES):
> This command specifies the relative path
>
>
>
> as a link directory.
>
> Policy CMP0015 is not set: link_directories() treats paths relative to
> the
> source dir. Run "cmake --help-policy CMP0015" for policy details. Use
> the
>
> cmake_policy command to set the policy and suppress this warning.
> This warning is for project developers. Use -Wno-dev to suppress it.
>
> Building component orocos-logging in library orocos-logging-gnulinux
> Building library orocos-log4cpp
> -- Found Lua51: /usr/lib/liblua5.1.so;/usr/lib/libm.so
> Building component orocos-lua in library orocos-lua-gnulinux
> Building plugin library rttlua-plugin
> Selected Libraries:
> -- Configuring incomplete, errors occurred!
> ard@ard-host-4:/opt/orocos2/install/log$
>
>
>> I have a successful build now. Maybe your luck will change this time ? :-]
>>
>
>
> I'll try again.
>

success :) , Thanks for your corrections.
...
autoproj: updated /opt/orocos2/env.sh
Build finished successfully at Thu Dec 16 12:03:09 +0100 2010
ard@ard-host-4:/opt/orocos2$

>
>>
>> Peter
>>
>>
>>
>

Orocos ToolChain2.2 error on Lua

2010/12/16 Willy Lambert <lambert [dot] willy [..] ...>

> I tried a new installation from zero and something seems to be wrong with
> boostrap :
> manifest /opt/orocos2/ocl/manifest.xml of ocl from orocos.toolchain lists
> 'lua-dev' as dependency, but it is neither a normal package nor an osdeps
> package. osdeps reports: there is no osdeps definition for lua-dev
> ard@ard-host-4:/opt/orocos2$
>
> complete log :
>
> ard@ard-host-4:/opt/orocos2$ wget
> http://gitorious.com/orocos-toolchain/build/blobs/raw/toolchain-2.2/boot...
> --2010-12-16 01:24:05--
> http://gitorious.com/orocos-toolchain/build/blobs/raw/toolchain-2.2/boot...
> Résolution de gitorious.com... 87.238.52.168
> Connexion vers gitorious.com|87.238.52.168|:80...connecté.
> requête HTTP transmise, en attente de la réponse...200 OK
> Un cookie provenant de gitorious.com a tenté de changer le domaine en
> gitorious.com
> Longueur: 589 [application/sh]
> Sauvegarde en : «bootstrap.sh»
>
> 100%[=========================================================================================================================================================================================>]
> 589 --.-K/s ds 0s
>
> 2010-12-16 01:24:07 (42,8 MB/s) - «bootstrap.sh» sauvegardé [589/589]
>
> ard@ard-host-4:/opt/orocos2$ sh bootstrap.sh
> --2010-12-16 01:24:10--
> http://doudou.github.com/autoproj/autoproj_bootstrap
> Résolution de doudou.github.com... 207.97.227.245
> Connexion vers doudou.github.com|207.97.227.245|:80...connecté.
> requête HTTP transmise, en attente de la réponse...200 OK
> Longueur: 52153 (51K) [application/octet-stream]
> Sauvegarde en : «autoproj_bootstrap»
>
> 100%[=========================================================================================================================================================================================>]
> 52 153 95,8K/s ds 0,5s
>
> 2010-12-16 01:24:11 (95,8 KB/s) - «autoproj_bootstrap» sauvegardé
> [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)
> installing OS packages: libopenssl-ruby1.8
>
> autoproj: installing autoproj and its dependencies (this can take a long
> time)
> looking for RubyGems updates
>
> 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: 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.gitbranch=toolchain-2.2
> local:
> /opt/orocos2/.remotes/git_git___gitorious_org__orocos_toolchain_autoproj_git_branch_toolchain_2_2
>
> defines: log4cpp, ocl, orogen, rtt, typelib, utilmm, utilrb
>
> autoproj: packages
> log4cpp
> defined in orocos.toolchain
> will be checked out in /opt/orocos2/log4cpp
>
> git:git://gitorious.org//orocos-toolchain/log4cpp.gitbranch=toolchain-2.2
> NOT checked out yet, reported dependencies will be partial
> ocl
> defined in orocos.toolchain
> will be checked out in /opt/orocos2/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 /opt/orocos2/orogen
>
> git:git://gitorious.org//orocos-toolchain/orogen.gitbranch=toolchain-2.2
> NOT checked out yet, reported dependencies will be partial
> rtt
> defined in orocos.toolchain
> will be checked out in /opt/orocos2/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 /opt/orocos2/typelib
>
> git:git://gitorious.org//orocos-toolchain/typelib.gitbranch=toolchain-2.2
> NOT checked out yet, reported dependencies will be partial
> utilmm
> defined in orocos.toolchain
> will be checked out in /opt/orocos2/utilmm
>
> git:git://gitorious.org//orocos-toolchain/utilmm.gitbranch=toolchain-2.2
> NOT checked out yet, reported dependencies will be partial
> utilrb
> defined in orocos.toolchain
> will be checked out in /opt/orocos2/utilrb
>
> git:git://gitorious.org//orocos-toolchain/utilrb.gitbranch=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 /opt/orocos2/env.sh
>
>
> WARNING: autoproj will not work until your restart all
> your consoles, or run the following in them:
> $ source /opt/orocos2/env.sh
>
>
> To import and build the packages, you can now run
> autoproj update
> autoproj build
>
> The resulting software is installed in
> /opt/orocos2/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
>
> manifest /opt/orocos2/ocl/manifest.xml of ocl from orocos.toolchain lists
> 'lua-dev' as dependency, but it is neither a normal package nor an osdeps
> package. osdeps reports: there is no osdeps definition for lua-dev
>
> 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
>
> manifest /opt/orocos2/ocl/manifest.xml of ocl from orocos.toolchain lists
> 'lua-dev' as dependency, but it is neither a normal package nor an osdeps
> package. osdeps reports: there is no osdeps definition for lua-dev
> ard@ard-host-4:/opt/orocos2$
>
>
> 2010/12/14 Sylvain Joyeux <sylvain [dot] joyeux [..] ...>
>
> 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.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
>> >
>> > 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.
>>
>> --
>> 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
>>
>
>
Here are additional information about my system :

ard@ard-host-4:/opt/orocos2$ sudo dpkg -l | grep lua
ii liblua5.1-0
5.1.4-5 Simple, extensible, embeddable
programming language
ard@ard-host-4:/opt/orocos2$ autoproj --version
autoproj v1.7.2

Orocos ToolChain2.2 error on Lua

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.

Orocos ToolChain2.2 error on Lua

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 ?

Peter

Orocos ToolChain2.2 error on Lua

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

Orocos ToolChain2.2 error on Lua

On Tuesday 14 December 2010 10:56:26 Sylvain Joyeux wrote:
> 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/boot
> >> st 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.

Great ! I'm looking forward to it.

Peter

Ruben Smits's picture

Orocos ToolChain2.2 error on Lua

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

Orocos ToolChain2.2 error on Lua

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
>