Hi,
two questions:
1) Sylvain, I have tried to bootstrap toolchain (2.1.1) and evething have
worked but in debian squeeze it has not been detected that libreadline-dev
was not installed. Did we forget this dependency? it's for ocl. Please, could
you look on it?
2) if autoproj fails in one step (ocl, for example) what I have to do to rerun
in the same step?
Regards,
Leo
bootstrap win toolchain 2.1.1 error
On 11/29/2010 01:28 PM, Leopold Palomo-Avellaneda wrote:
> Hi,
>
> two questions:
>
> 1) Sylvain, I have tried to bootstrap toolchain (2.1.1) and evething have
> worked but in debian squeeze it has not been detected that libreadline-dev
> was not installed. Did we forget this dependency? it's for ocl. Please, could
> you look on it?
I just checked out an orocos-toolchain to have a look. Yes, OCL is
indeed totally broken in that respect: there are no osdeps whatsoever.
So, it is just that everybody who did build it until now already had
readline installed.
On the latest autoproj version (which you have if you have run autoproj
update at least once the last weeks), you can have a look for yourself
by doing
autoproj osdeps --show
and
autoproj osdeps --rshow
I just realized I never sent the changelog to the mailing list. I'll
make an announcement soonish.
> 2) if autoproj fails in one step (ocl, for example) what I have to do to rerun
> in the same step?
doing "autoproj build" will rebuild only what has changed.
Otherwise, you can do
autoproj [operation] [package]
in which case the operation will be applied only on the package and its
dependencies. I.e.
autoproj build ocl
should do the trick for you
Note: you should have a quick look at
http://rock-robotics.org/autoproj/quick_start.html
--
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
bootstrap win toolchain 2.1.1 error
A Dilluns 29 Novembre 2010, Sylvain Joyeux va escriure:
> On 11/29/2010 01:28 PM, Leopold Palomo-Avellaneda wrote:
> > Hi,
> >
> > two questions:
> >
> > 1) Sylvain, I have tried to bootstrap toolchain (2.1.1) and evething have
> > worked but in debian squeeze it has not been detected that
> > libreadline-dev was not installed. Did we forget this dependency? it's
> > for ocl. Please, could you look on it?
>
> I just checked out an orocos-toolchain to have a look. Yes, OCL is
> indeed totally broken in that respect: there are no osdeps whatsoever.
> So, it is just that everybody who did build it until now already had
> readline installed.
>
> On the latest autoproj version (which you have if you have run autoproj
> update at least once the last weeks), you can have a look for yourself
> by doing
>
> autoproj osdeps --show
>
> and
>
> autoproj osdeps --rshow
>
> I just realized I never sent the changelog to the mailing list. I'll
> make an announcement soonish.
Ok,
I'm having another error with autoproj. I cannot run anything because:
leo@talp:~/robotica/orocos/orocos-toolchain$ autoproj update
autodetecting the operating system
Which prepackaged software (a.k.a. 'osdeps') should autoproj install
automatically (all, ruby, os, none) ? all
looking for RubyGems updates
autoproj: loading ...
run 'autoproj --reconfigure' to change configuration values
autoproj: importing and loading selected packages
autoproj: nothing to do
Build finished successfully at Mon Nov 29 15:31:41 +0100 2010
leo@talp:~/robotica/orocos/orocos-toolchain$ autoproj --reconfigure
unknown mode
run autoproj --help for more documentation
leo@talp:~/robotica/orocos/orocos-toolchain$ autoproj --reconfigure
unknown mode
run autoproj --help for more documentation
> > 2) if autoproj fails in one step (ocl, for example) what I have to do to
> > rerun in the same step?
>
> doing "autoproj build" will rebuild only what has changed.
>
> Otherwise, you can do
>
> autoproj [operation] [package]
>
> in which case the operation will be applied only on the package and its
> dependencies. I.e.
>
> autoproj build ocl
>
> should do the trick for you
ok, but I'm blocked in the --reconfigure step.
> Note: you should have a quick look at
> http://rock-robotics.org/autoproj/quick_start.html
yes ....
bootstrap win toolchain 2.1.1 error
On 11/29/2010 03:51 PM, Leopold Palomo-Avellaneda wrote:
> leo@talp:~/robotica/orocos/orocos-toolchain$ autoproj update
> autodetecting the operating system
> Which prepackaged software (a.k.a. 'osdeps') should autoproj install
> automatically (all, ruby, os, none) ? all
> looking for RubyGems updates
> autoproj: loading ...
> run 'autoproj --reconfigure' to change configuration values
>
> autoproj: importing and loading selected packages
> autoproj: nothing to do
> Build finished successfully at Mon Nov 29 15:31:41 +0100 2010
> leo@talp:~/robotica/orocos/orocos-toolchain$ autoproj --reconfigure
> unknown mode
> run autoproj --help for more documentation
OK, wrong message. I'll have to fix that.
You could run
autoproj update --reconfigure
(or, for that matter, autoproj build --reconfigure, autoproj osdeps
--reconfigure and so on).
Now, that's probably not your problem right now. I'm really wondering
what's going on: 'nothing to do' is displayed when there are no packages
to build (i.e. no packages in manifest).
Can you send me
the output of autoproj --version
your complete 'autoproj' directory ?
Thanks
--
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
bootstrap win toolchain 2.1.1 error (with the file ....)
A Dilluns 29 Novembre 2010, Sylvain Joyeux va escriure:
> your complete 'autoproj' directory ?
>
bootstrap win toolchain 2.1.1 error
A Dilluns 29 Novembre 2010, Sylvain Joyeux va escriure:
> On 11/29/2010 03:51 PM, Leopold Palomo-Avellaneda wrote:
> > leo@talp:~/robotica/orocos/orocos-toolchain$ autoproj update
> > autodetecting the operating system
> > Which prepackaged software (a.k.a. 'osdeps') should autoproj install
> > automatically (all, ruby, os, none) ? all
> > looking for RubyGems updates
> > autoproj: loading ...
> > run 'autoproj --reconfigure' to change configuration values
> >
> > autoproj: importing and loading selected packages
> > autoproj: nothing to do
> > Build finished successfully at Mon Nov 29 15:31:41 +0100 2010
> > leo@talp:~/robotica/orocos/orocos-toolchain$ autoproj --reconfigure
> > unknown mode
> > run autoproj --help for more documentation
>
> OK, wrong message. I'll have to fix that.
>
> You could run
>
> autoproj update --reconfigure
>
> (or, for that matter, autoproj build --reconfigure, autoproj osdeps
> --reconfigure and so on).
ok,
I have run both, but no good results:
####################################
autoproj update --reconfigure
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]
looking for RubyGems updates
autoproj: loading ...
autoproj: importing and loading selected packages
autoproj: nothing to do
Build finished successfully at Mon Nov 29 17:01:05 +0100 2010
leo@talp:~/robotica/orocos/orocos-toolchain$ autoproj build ocl
autodetecting the operating system
Which prepackaged software (a.k.a. 'osdeps') should autoproj install
automatically (all, ruby, os, none) ? all
autoproj: loading ...
run 'autoproj --reconfigure' to change configuration values
autoproj: wrong package selection on command line
leo@talp:~/robotica/orocos/orocos-toolchain$ autoproj --reconfigure
unknown mode
run autoproj --help for more documentation
leo@talp:~/robotica/orocos/orocos-toolchain$ autoproj osdeps
autodetecting the operating system
Which prepackaged software (a.k.a. 'osdeps') should autoproj install
automatically (all, ruby, os, none) ? all
autoproj: loading ...
run 'autoproj --reconfigure' to change configuration values
autoproj: importing and loading selected packages
autoproj: nothing to do
Build finished successfully at Mon Nov 29 17:02:27 +0100 2010
leo@talp:~/robotica/orocos/orocos-toolchain$ autoproj osdeps --reconfigure
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: loading ...
autoproj: importing and loading selected packages
autoproj: nothing to do
Build finished successfully at Mon Nov 29 17:02:36 +0100 2010
leo@talp:~/robotica/orocos/orocos-toolchain$ autoproj build ocl
autodetecting the operating system
Which prepackaged software (a.k.a. 'osdeps') should autoproj install
automatically (all, ruby, os, none) ? all
autoproj: loading ...
run 'autoproj --reconfigure' to change configuration values
autoproj: wrong package selection on command line
> Now, that's probably not your problem right now. I'm really wondering
> what's going on: 'nothing to do' is displayed when there are no packages
> to build (i.e. no packages in manifest).
>
> Can you send me
>
> the output of autoproj --version
leo@talp:~/robotica/orocos/orocos-toolchain$ autoproj --version
autoproj v1.6.2
> your complete 'autoproj' directory ?
privately ...
bootstrap win toolchain 2.1.1 error
On 11/29/2010 05:05 PM, Leopold Palomo-Avellaneda wrote:
> A Dilluns 29 Novembre 2010, Sylvain Joyeux va escriure:
>> On 11/29/2010 03:51 PM, Leopold Palomo-Avellaneda wrote:
>>> leo@talp:~/robotica/orocos/orocos-toolchain$ autoproj update
>>> autodetecting the operating system
>>> Which prepackaged software (a.k.a. 'osdeps') should autoproj install
>>> automatically (all, ruby, os, none) ? all
>>> looking for RubyGems updates
>>> autoproj: loading ...
>>> run 'autoproj --reconfigure' to change configuration values
>>>
>>> autoproj: importing and loading selected packages
>>> autoproj: nothing to do
>>> Build finished successfully at Mon Nov 29 15:31:41 +0100 2010
>>> leo@talp:~/robotica/orocos/orocos-toolchain$ autoproj --reconfigure
>>> unknown mode
>>> run autoproj --help for more documentation
>>
>> OK, wrong message. I'll have to fix that.
>>
>> You could run
>>
>> autoproj update --reconfigure
>>
>> (or, for that matter, autoproj build --reconfigure, autoproj osdeps
>> --reconfigure and so on).
>
> ok,
>
> I have run both, but no good results:
Ah. I have not been clear enough.
The problem was certainly not a bad configuration
How did you bootstrap this ? There is only an empty manifest, which
explains why nothing gets built ...
--
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
bootstrap win toolchain 2.1.1 error
On 11/29/2010 05:27 PM, Sylvain Joyeux wrote:
> On 11/29/2010 05:05 PM, Leopold Palomo-Avellaneda wrote:
>> A Dilluns 29 Novembre 2010, Sylvain Joyeux va escriure:
>>> On 11/29/2010 03:51 PM, Leopold Palomo-Avellaneda wrote:
>>>> leo@talp:~/robotica/orocos/orocos-toolchain$ autoproj update
>>>> autodetecting the operating system
>>>> Which prepackaged software (a.k.a. 'osdeps') should autoproj install
>>>> automatically (all, ruby, os, none) ? all
>>>> looking for RubyGems updates
>>>> autoproj: loading ...
>>>> run 'autoproj --reconfigure' to change configuration values
>>>>
>>>> autoproj: importing and loading selected packages
>>>> autoproj: nothing to do
>>>> Build finished successfully at Mon Nov 29 15:31:41 +0100 2010
>>>> leo@talp:~/robotica/orocos/orocos-toolchain$ autoproj --reconfigure
>>>> unknown mode
>>>> run autoproj --help for more documentation
>>>
>>> OK, wrong message. I'll have to fix that.
>>>
>>> You could run
>>>
>>> autoproj update --reconfigure
>>>
>>> (or, for that matter, autoproj build --reconfigure, autoproj osdeps
>>> --reconfigure and so on).
>>
>> ok,
>>
>> I have run both, but no good results:
> Ah. I have not been clear enough.
>
> The problem was certainly not a bad configuration
Ah... Let me rephrase this.
The problem was not that there was a bad choice of configuration
options. Which is what --reconfigure changes.
If you want to switch the configuration source (i.e. where the autoproj/
directory comes from), use switch-config.
--
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
bootstrap win toolchain 2.1.1 error
On 11/29/2010 02:43 PM, Sylvain Joyeux wrote:
>> 1) Sylvain, I have tried to bootstrap toolchain (2.1.1) and evething have
>> worked but in debian squeeze it has not been detected that libreadline-dev
>> was not installed. Did we forget this dependency? it's for ocl. Please, could
>> you look on it?
> I just checked out an orocos-toolchain to have a look. Yes, OCL is
> indeed totally broken in that respect: there are no osdeps whatsoever.
> So, it is just that everybody who did build it until now already had
> readline installed.
Pushed a fix for readline. Don't know if other dependencies are needed
--
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