[Rock-dev] autoproj build failed on master branch
Willy Lambert
lambert.willy at gmail.com
Mon Dec 13 21:04:39 CET 2010
I tried to follow theses instructions :
http://rock-robotics.org/startup/index.html
I choosed the master branch on Sylvain's advice because merging is in
progress. But bootstrapping failed when using eigen2. I have a personnal
installation of eigen on my system, could anything be badly interacting with
this ?
ard at ard-host-4:/opt/rock$ sh bootstrap.sh
--2010-12-13 20:39:36-- http://www.rock-robotics.org/autoproj_bootstrap
Résolution de www.rock-robotics.org... 80.67.28.127
Connexion vers www.rock-robotics.org|80.67.28.127|:80...connecté.
requête HTTP transmise, en attente de la réponse...200 OK
Longueur: 50426 (49K) [text/plain]
Sauvegarde en : «autoproj_bootstrap»
100%[=========================================================================================================================================================================================>]
50 426 221K/s ds 0,2s
2010-12-13 20:39:36 (221 KB/s) - «autoproj_bootstrap» sauvegardé
[50426/50426]
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 import data from gitorious (git, http or ssh)
Use 'ssh' only if you have a gitorious account. Note that
ssh will always be used to push to the repositories, this is
only to get data from gitorious. Therefore, we advise to use
'git' as it is faster than ssh and better than http [git]
Which flavor of Rock do you want to use ?
The 'stable' flavor is not updated often, but will contain well-tested
code
The 'next' flavor is updated more often, and might contain less tested
code
it is updated from 'master' to test new features before they get pushed
in 'stable'
Finally, 'master' is where the development takes place. It should
generally be in
a good state, but will break every once in a while
See http://rock-robotics.org/startup/releases.html for more information
[stable] master
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
rock.toolchain (listed in manifest)
from: git:git://gitorious.org//rock-toolchain/package_set.gitbranch=master
push_to=git at gitorious.org:
/rock-toolchain/package_set.git
local:
/opt/rock/.remotes/git_git___gitorious_org__rock_toolchain_package_set_git_branch_master_push_to_git_gitorious_org__rock_toolchain_package_set_git
imports 2 package sets
orocos.toolchain
rock.base
defines: base/orogen/types, tools/logger, tools/orocos.rb, tools/pocolog,
tools/reigen, tools/roby
rock.base (imported by rock.toolchain)
from: git:git://gitorious.org//rock-base/package_set.gitpush_to=git@gitorious.org:
/rock-base/package_set.git
local:
/opt/rock/.remotes/git_git___gitorious_org__rock_base_package_set_git_push_to_git_gitorious_org__rock_base_package_set_git
defines: base/scripts, base/types, external/sisl
autoproj: packages
base/orogen/types
defined in rock.toolchain
will be checked out in /opt/rock/base/orogen/types
git:git://gitorious.org//rock-toolchain/orogen-base-types.gitbranch=master
push_to=git at gitorious.org:
/rock-toolchain/orogen-base-types.git
NOT checked out yet, reported dependencies will be partial
disabled opt deps: ocl
base/scripts
defined in rock.base
will be checked out in /opt/rock/base/scripts
git:git://gitorious.org//rock/scripts.git branch=master
push_to=git at gitorious.org:/rock/scripts.git
NOT checked out yet, reported dependencies will be partial
base/types
defined in rock.base
will be checked out in /opt/rock/base/types
git:git://gitorious.org//rock-base/types.git branch=master
push_to=git at gitorious.org:/rock-base/types.git
NOT checked out yet, reported dependencies will be partial
external/sisl
defined in rock.base
will be checked out in /opt/rock/external/sisl
archive:
http://www.sintef.no/upload/IKT/9011/geometri/sisl/sisl_4.4_GPL.tgzpatches=/opt/rock/.remotes/git_git___gitorious_org__rock_base_package_set_git_push_to_git_gitorious_org__rock_base_package_set_git/sisl-01-build_shlibs-02.patch
update_cached_file=false
NOT checked out yet, reported dependencies will be partial
tools/logger
defined in rock.toolchain
will be checked out in /opt/rock/tools/logger
git:git://gitorious.org//rock-toolchain/orogen-logger.git branch=master
push_to=git at gitorious.org:/rock-toolchain/orogen-logger.git
NOT checked out yet, reported dependencies will be partial
disabled opt deps: ocl
tools/orocos.rb
defined in rock.toolchain
will be checked out in /opt/rock/tools/orocos.rb
git:git://gitorious.org//rock-toolchain/orocos-rb.git branch=master
push_to=git at gitorious.org:/rock-toolchain/orocos-rb.git
NOT checked out yet, reported dependencies will be partial
tools/pocolog
defined in rock.toolchain
will be checked out in /opt/rock/tools/pocolog
git:git://gitorious.org//rock-toolchain/pocolog.git branch=master
push_to=git at gitorious.org:/rock-toolchain/pocolog.git
NOT checked out yet, reported dependencies will be partial
tools/reigen
defined in rock.toolchain
will be checked out in /opt/rock/tools/reigen
git:git://gitorious.org//rock-toolchain/reigen.git branch=master
push_to=git at gitorious.org:/rock-toolchain/reigen.git
NOT checked out yet, reported dependencies will be partial
tools/roby
defined in rock.toolchain
will be checked out in /opt/rock/tools/roby
git:git://gitorious.org//rock-toolchain/roby.git branch=master
push_to=git at gitorious.org:/rock-toolchain/roby.git
NOT checked out yet, reported dependencies will be partial
WARN: the following packages are not yet checked out:
WARN: base/orogen/types, base/scripts, base/types, external/sisl
WARN: tools/logger, tools/orocos.rb, tools/pocolog, tools/reigen
WARN: tools/roby
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/rock/env.sh
WARNING: autoproj will not work until your restart all
your consoles, or run the following in them:
$ source /opt/rock/env.sh
To import and build the packages, you can now run
autoproj update
autoproj build
The resulting software is installed in
/opt/rock/install
Access method to import data from gitorious (git, http or ssh): git
Which flavor of Rock do you want to use ? master
autodetecting the operating system
looking for RubyGems updates
updating autoproj main configuration
autoproj: updating remote definitions of package sets
updating rock.toolchain
updating rock
rock.toolchain: auto-importing orocos.toolchain
updating orocos.toolchain
rock.toolchain: auto-importing rock.base
updating rock.base
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 base/orogen/types
checking out base/scripts
checking out base/types
checking out external/sisl
patching external/sisl
WARN: external/sisl from rock.base does not have a manifest
checking out tools/logger
checking out tools/orocos.rb
checking out tools/pocolog
checking out tools/reigen
checking out tools/roby
checking out orogen
checking out rtt
checking out typelib
checking out utilmm
checking out utilrb
installing OS packages: graphviz, libeigen2-dev, libqt4-ruby1.8,
omniorb4-nameserver
Build failed: autoproj: failed in osdeps phase
'/bin/bash /tmp/osdeps_sh20101213-17072-kw7o89-0' returned status 100
see /opt/rock/install/log/autoproj-osdeps.log for details
last 5 lines are:
Mon Dec 13 20:41:39 +0100 2010: running
/bin/bash /tmp/osdeps_sh20101213-17072-kw7o89-0
E: Impossible d'obtenir le verrou /var/lib/dpkg/lock - open (11:
Ressource temporairement non disponible)
E: Impossible de verrouiller le répertoire d'administration
(/var/lib/dpkg/). Il est possible qu'un autre processus l'utilise.
Access method to import data from gitorious (git, http or ssh): git
Which flavor of Rock do you want to use ? master
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
WARN: external/sisl from rock.base does not have a manifest
autoproj: building and installing packages
generating and configuring build system for utilmm
building utilmm (100%)
installing utilmm
building external/sisl
installing external/sisl
generating and configuring build system for base/types
Build failed: base/types: failed in configure phase
'cmake -DCMAKE_INSTALL_PREFIX=/opt/rock/install
-DSISL_PREFIX=/opt/rock/install /opt/rock/base/types' returned status 1
see /opt/rock/install/log/base/types-configure.log for details
last 10 lines are:
-- Performing Test CXX_SUPPORTS_WALL - Success
-- Boost version: 1.42.0
CMake Error at
/usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:70
(MESSAGE):
Could NOT find Eigen2 (missing: EIGEN2_INCLUDE_DIR)
Call Stack (most recent call first):
cmake/FindEigen2.cmake:23 (find_package_handle_standard_args)
CMakeLists.txt:19 (find_package)
-- Configuring incomplete, errors occurred!
ard at ard-host-4:/opt/rock$
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.dfki.de/mailman/cgi-bin/private/rock-dev/attachments/20101213/09d1658f/attachment-0001.htm
More information about the Rock-dev
mailing list