-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bootstrap.sh for toolchain-2.8 throws builder errors on a clean system #1
Comments
I have this issue too. Did you solve it for you somehow? |
Here's the instructions I wrote for my group, the "overrides.yml" file is attached (rename it to remove the .txt extension).Currently (Jan. 2016), installing the Orocos toolchain 2.8 from GitHub is broken. This is an installation procedure with a couple of "hacks" that will make it work on a fresh Ubuntu 14.04 install. Firstly, install git and ruby:
Set up the git username and email:
Create a directory for the Orocos files to go and clone the GitHub repository with the bootstrap script:
Run the bootstrap:
Press 'Enter' to select the default options whenever the script stops to ask you. At some point the script WLLL FAIL. We were expecting this. A Ruby utility called Autoproj should have already downloaded some folders. Go into the Autoproj folder:
There should be a file called 'overrides.yml'. Replace it with overrides.yml.txt (remove the .txt extension). If you look in the replacement 'overrides.yml', you should see a list of Orocos GitHub repository names with the 'branch' option set to 'toolchain-2.8'. The reason Autoproj failed earlier is because it is pulling from the 'master' branch on the Orocos GitHub, which has different dependencies than the 2.8 branch. The 'overrides' file will force Autoproj to use the correct branch when it clones the repositories. Start autoproj again, this time manually:
You should get another error similar to the first. Change to the metaruby directory:
This package didn't come from Orocos, and it still has the dependency issue, so we're going to fix that ourselves. Edit the 'manifest.xml' and delete the following line:
Also edit 'Rakefile' and remove:
You will need root privileges to do so (use sudo in front of your editor command). Return to the build folder and build Orocos:
That should do it! |
I follow the instruction of thedman9052 but I got an error while executing autoproj update
I already installed ruby-facets by the following command: My system information:
|
Is that officially supported for toolchain 2.8 ? In any case, this is weird. It attempts to install ruby-facets, but the osdeps list the gem for 'facets'. Could you post the complete autoproj output for |
Hi doudou, Actually, when I moved to Ubuntu 14.04, there was no such kind of error. Anyway, below is the output for
|
I have no experience with autoproj, but I could install the toolchain version 2.8 successfully with the above instructions in Ubuntu 12.04. Maybe the OS detection somehow fails, because in the output you posted it says
while on my test system (12.04 with Ruby 1.9.1 installed from package
? That would explain why autoproj tries to install the non-existing system package
(from https://github.com/orocos-toolchain/autoproj/blob/master/orocos.osdeps#L138) |
As there is no official list of target platforms that I know of, it is hard to say :-) But I do not see a reason why it should not be supported. For ROS releases we should at least stay compatible with the ROS target platforms, as detailed in REP 3 - Target Platforms. ROS Hydro was released with Orocos Toolchain 2.7, while ROS Indigo and Jade got 2.8 and the pending ROS Kinetic release is waiting for 2.9. So version 2.8 should be targeted at least for Ubuntu Saucy (13.10) and newer. |
On a fresh install of Ubuntu 14.04 with Ruby 1.9, using bootstrap.sh from the toolchain-2.8 branch does not build successfully. Autoproj throws an error:
The Autoproj logfiles indicate that Autoproj is pulling orocos-toolchain packages from the master branch instead of toolchain-2.8.
utilrb-import.log.txt (Renamed so GitHub would let me upload)
Packages in the master branch have a dependency on builder, while packages from the toolchain-2.8 branch do not (they depend on hoe and rake instead).
Adding branch overrides to the Autoproj overrides.yml fixes the orocos-toolchain package dependency issues, but it does not fix a bundler dependency issue with metaruby.
The text was updated successfully, but these errors were encountered: