-
Notifications
You must be signed in to change notification settings - Fork 60
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
*** extconf.rb failed *** #14
Comments
Looks like a problem building ruby-libvirt, can you install/build it separately? |
I did install ruby-libvirt, but the error remains:
|
Same error message? |
Yes indeed. |
I'm afraid I'm not really qualified to help, I'm currently trying to understand the issues around gems. Some will be installed by your package manager, some system-wide by the It looks like Vagrant need the gems in ~/.vagrant.d/gems/ and there may be some paths it's not aware of when trying to build dependencies. I have to admit I installed ruby-libvirt and nokogiri before installing vagrant-kvm on my system. I need to test these issues some more. Hopefully I'll narrow down the issues. |
I just look a bit deeper inside the error messages. It's to be a problem of my Vagrant installation not able to run the ruby-libvirt installation. I guess the ArchLinux guys did manage to have own ruby bin inside the vagrant folder to make it independence of the reset of ruby. That's why it can't access the system wide installed gem. I'll report a bug in Arch. Before I'm going to try another way of installing it. Maybe that will work. Thank you for your help. |
Actually, Vagrant now installs a self-contained environment in |
hm...than it's maybe an issue of the vagrant installation? I'm now getting the error message that Vagrant isn't installed in the right way.
I found some issue with this, but maybe I have to check Vagrant first. |
I was able to fix it. I de-installed I'm not sure, I only can guess. But maybe Thanks for the help. |
Just in case someone else gets the same error, this is how I've made the plugin build:
|
Thank you! I ran into the same problem with Vagrant 1.3.5 on Arch Linux, and this tip worked like a charm! |
Hit this problem when installing vagrant-libvirt and it failed to installed ruby-libvirt and discovered that the problem system was missing The hint is that the listed configuration options:
Has nothing listed for |
I do have following issue:
I serachf or the file:
⮀sudo find / -xdev -name libvirt.h
/usr/include/libvirt/libvirt.h
virNetworkPtr is define inside of the header. ....
any idea?
More info:
vagrant -v
Vagrant version 1.2.2
Linux jax 3.9.5-1-ARCH #1 SMP PREEMPT Sat Jun 8 09:22:45 CEST 2013 x86_64 GNU/Linux
libvirtd --version libvirtd (libvirt) 1.0.6
qemu 1.5.0-4
The text was updated successfully, but these errors were encountered: