Skip to content
This repository has been archived by the owner on Mar 12, 2019. It is now read-only.

spiceweasal binary failing to load #88

Open
csmyth95 opened this issue Jul 23, 2015 · 4 comments
Open

spiceweasal binary failing to load #88

csmyth95 opened this issue Jul 23, 2015 · 4 comments

Comments

@csmyth95
Copy link

Hi, I am trying to run a .json file that I coded for use with spiceweasal for chef deployments. Whenever I try to use spiceweasel on my git bash shell, I get a file load error from the spiceweasal binary where it says "require 'spiceweasal'" (line 21). (Error shown below)

image

I cloned the repo for spiceweasal (version 2.8) from Github using git clone and installed its dependencies using bundler. The spiceweasal bin directory is also in my environment variables PATH.
I would greatly appreciate any help you could offer me, Thanks.

@andyglick
Copy link

do you want to use spiceweasel as an application or do you want to work at developing it? If all you want to do is use it as an application to support your chef work you should be able to install the spiceweasel gem, and you won't need to execute the binary from the github clone

gem install spiceweasel 

I have successfully installed and have been able to invoke spiceweasel using the installed gem

@csmyth95
Copy link
Author

Hi Andy,

I want to use spiceweasel as an application for deploying my chef cookbooks.

I ran "gem install spiceweasel" in my bash shell on Windows 7 and the following happened.

image

I have tried installing both Gecode version 4.4.0 and 3.5.0 and neither have worked for me.

Do you have any suggestions?

@mattray
Copy link
Owner

mattray commented Jul 29, 2015

I know that the Chef client for Windows hasn't been upgraded to Ruby 2.1 (or 2.2) yet because of stability issues (Linux is on 2.1). Perhaps try using Ruby 2.0 on Windows?

@csmyth95
Copy link
Author

Hi Matt, I installed Ruby 2.0 using the ruby installer. I then tried installing spiceweasel using "gem install spiceweasel" (after removing the git cloned repo of spiceweasel I used to have) and when it tries to build native extensions for dep_selector-1.0.3.gem, It fails to build even with Ruby 2.0 in the build path (as shown below).

image

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