Skip to content
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 orocos-toolchain2.8 throws ruby errors on ubuntu 16.04 #2

Open
srobaudo opened this issue Jun 29, 2016 · 8 comments
Open

Comments

@srobaudo
Copy link

srobaudo commented Jun 29, 2016

Trace pasted below:

~/orocos/build$ ./bootstrap.sh 
--2016-06-29 00:33:13--  http://rock-robotics.org/stable/autoproj_bootstrap
Resolving rock-robotics.org (rock-robotics.org)... 46.252.18.41, 2a00:1158:1000:300::129
Connecting to rock-robotics.org (rock-robotics.org)|46.252.18.41|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://raw.githubusercontent.com/rock-core/autoproj/stable/bin/autoproj_bootstrap [following]
--2016-06-29 00:33:14--  https://raw.githubusercontent.com/rock-core/autoproj/stable/bin/autoproj_bootstrap
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 151.101.56.133
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.56.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 118844 (116K) [text/plain]
Saving to: ‘autoproj_bootstrap’

autoproj_bootstrap  100%[===================>] 116,06K   222KB/s    in 0,5s    

2016-06-29 00:33:15 (222 KB/s) - ‘autoproj_bootstrap’ saved [118844/118844]

The current directory is not empty, continue bootstrapping anyway ? [yes] 
  autodetecting the operating system
  operating system: ubuntu,debian - 16.04,lts,xenial,xerus
  Which prepackaged software (a.k.a. 'osdeps') should autoproj install automatically (all, none or a comma-separated list of: os gem pip) ?
    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 "pip", only the Ruby packages will be installed.
      Installing these packages does not require root access.
    * if you say "gem", 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.

    Finally, you can provide a comma-separated list of pip gem and os.

    As any configuration value, the mode can be changed anytime by calling
      autoproj reconfigure

    Finally, the "autoproj osdeps" command will give you the necessary information
    about the OS packages that you will need to install manually.

    So, what do you want ? (all, none or a comma-separated list of: os gem pip) [all] 
autoproj: installing a proper Ruby environment (this can take a long time)
failed: there is no osdeps definition for ruby23 (search tree: ruby->ruby23)
./bootstrap.sh: 45: .: Can't open /home/proy/orocos/build/env.sh

After the failure, autoproj has still not been created, hence the steps to follow explained in #1 cannot be used.

@srobaudo srobaudo closed this as completed Jul 4, 2016
@doudou
Copy link
Contributor

doudou commented Jul 4, 2016

Closed because fixed ?

The autoproj bootstrap script was not supporting ruby 2.3. I fixed it last week but I could not test it because of other problems.

@srobaudo
Copy link
Author

srobaudo commented Jul 4, 2016

Closed because couldn't fix it, and did not receive answers.
Changed to Ubuntu 14.04 image, and followed instructions in #1
Only needed change, is installing Ruby version using RVM instead of apt-get

@srobaudo srobaudo reopened this Jul 4, 2016
@Aladdin-Ark
Copy link

I have the same problem now on Linux Mint 18 (Sarah).
The autoproj script is not supporting by ruby 2.3 but I could successfully fix it for bootstrap script and for building the toolchain 2.8 but after that i faced the same issue for building my typekit library since it will use the script during the build.

I would appreciate if there is any solution to make it work stable on Linux Mint 18 or Ubuntu 16.04

@doudou
Copy link
Contributor

doudou commented Aug 10, 2016

I finally managed to get a Vagrant environment on 16.04. I started bootstrapping a master installation

  • the original problem (lack of ruby2.3 osdep) is fixed
  • pkg-config was not defined in the osdep [https://github.com/add an osdep for pkg-config autoproj#21]
  • must use castxml on 16.04. Add Autoproj.env_set 'TYPELIB_CXX_LOADER', 'castxml' at the end of autoproj/init.rb

@doudou
Copy link
Contributor

doudou commented Aug 10, 2016

i faced the same issue for building my typekit library since it will use the script during the build.

I don't understand this. Apart from the 'autoproj build' / 'amake' call, autoproj itself is not involved in the build process (i.e. if it can build the toolchain, it should be able to build your packages)

@Aladdin-Ark
Copy link

Yes that's right.
I can build the packages but typekit.
During building the typekit I can see it is using some scripts to create
corba transportation files. I am not sure how it is working but seems there
is a problem on it.

Did you managed it to work? If you can provide any files, I really
appreciate it.

Thanks

On Aug 11, 2016 8:27 AM, "Sylvain Joyeux" [email protected] wrote:

i faced the same issue for building my typekit library since it will use
the script during the build.

I don't understand this. Apart from the 'autoproj build' / 'amake' call,
autoproj itself is not involved in the build process (i.e. if it can build
the toolchain, it should be able to build your packages)


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#2 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFRJtVj0wf1ftPkzQfA2RtlVkJvkWy8Jks5qel5LgaJpZM4JAvjO
.

@doudou
Copy link
Contributor

doudou commented Aug 11, 2016

toolchain-2.8 is a completely different beast. The package set definitions are too out-of-date, no chance to build the toolchain using them on 16.04.

I've prepared a buildconf that allows to build something close to toolchain-2.8 on 16.04. This is quickly done, so I can't really promise anything. It's basically toolchain-2.8 plus two packages on master (orogen and typelib)

The stuff is on the toolchain-2.8-16.04 branch of this repository. You can bootstrap using this script: https://raw.githubusercontent.com/orocos-toolchain/build/toolchain-2.8-16.04/bootstrap.sh

I've done very limited testing given that I'm not an orocos toolchain user myself (Rock developer). You do need to find a way to import the 'std' typekit and add the 'std' dependency to all your packages. The latter can be done easily in autoproj, see autoproj/overrides.rb for an example. The former, I don't know.

@smits, @meyerj this stuff might be of interest to you.

@roboticsai
Copy link

apt-get install ruby ruby-dev
gem install rake hoe

it will solve your problem also i think. I reinstalled the ubuntu 16.06 thinking that it will remove the ruby error, but not. So afteer i run above two commands the ruby eror is gone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants