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

Vagrant 1.6.5 under Windows 7 cannot handle standard paths properly #4766

Closed
zerkms opened this issue Nov 1, 2014 · 5 comments
Closed

Vagrant 1.6.5 under Windows 7 cannot handle standard paths properly #4766

zerkms opened this issue Nov 1, 2014 · 5 comments

Comments

@zerkms
Copy link

zerkms commented Nov 1, 2014

When I run

vagrant plugin install vagrant-cachier

command it fails with the following error:

"C:/Program Files (x86)/vagrant/embedded/bin/ruby.exe" extconf.rb 
creating Makefile

make "DESTDIR="
generating generator-i386-mingw32.def
/bin/sh: -c: line 0: syntax error near unexpected token `x86'
/bin/sh: -c: line 0: `/C/Program\ Files\ (x86)/vagrant/embedded/bin/ruby -e "puts 'EXPORTS', 'Init_generator'"  > generator-i386-mingw32.def'
make: *** [generator-i386-mingw32.def] Error 2
@sethvargo
Copy link
Contributor

@zerkms this is not a bug with Vagrant or Windows 7 specifically. This is a bug in Ruby where Ruby cannot compile gems with native extensions where there is a space ( ) or a parenthesis ((or)) in the path. Uninstall and re-install Vagrant intoC:/vagrant or another non-space directory and it should work as expected.

I'm sorry for the confusion. As soon as Ruby fixes the bug, Vagrant will automatically inherit the change.

@zerkms
Copy link
Author

zerkms commented Nov 2, 2014

@sethvargo any relevant bug in ruby bug tracker?

@sethvargo
Copy link
Contributor

@zerkms
Copy link
Author

zerkms commented Nov 2, 2014

@sethvargo thanks

PS: oh god, what is that special with spaces :-S

@CoDEmanX
Copy link

CoDEmanX commented Sep 8, 2015

I'm seeing this error although there are no parens or spaces in the ruby / rails / devkit path. Are dashes also fatal?

@ghost ghost locked and limited conversation to collaborators Apr 7, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants