-
Notifications
You must be signed in to change notification settings - Fork 254
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
npm install fails on Solaris (SmartOS) #100
Comments
If I remember correctly, solaris/joyent doesn't have libxml2 installed in any of the usual place. Would you mind finding out if the lib is installed and if so, what's the path to the include files? |
It was not installed by default, but I installed it with |
I tried installing libxmljs directly instead of as a dependency for another module and was able to get what appears to be a more informative set of error messages:
|
Can you tell me what the output of the following command gives on that machine?
Also, what version of libxml2 is being installed? |
Version 2.7.8 is installed. |
@goldfire and what does
Give you? I believe that however libxml2 was installed was not quite right. |
|
@goldfire sorry, I forgot to request a recursive ls
I would like to see if the header files are actually in the location they are supposed to be in. Is there a way for me to reproduce this issue on an instance? Can you provide access or does joyent have free instances I can test on? |
I'm running one of their paid Node.js instances that can only be logged into with an SSH key. The free instances at http://no.de are essentially the same thing, so it should reproduce the issue. |
@goldfire I fired up a free no.de instance. npm does not work out of the box. How are you installing libxmljs? |
Did you login to use node? |
@goldfire Yes, I followed the ssh instructions on the no.de website. Node works, npm does not. Regardless, I cloned the repo and did a simple 'make' and it built just fine. So the problem is with some other setup you have going on and not the package failing to build. As a note, the xml2-config app I have installed reported being located in /usr/bin/xml2-config and not in /opt |
@shtylman I guess the no.de setup is different from the paid ones. I get the following when I clone the repo and try what you said:
or with make
|
@goldfire you need to make sure that node-waf is in your PATH. |
Oh right, forgot I had logged into a different user. I still get this when installing from source instead of npm:
|
@goldfire can you do the build with
And pastbin the result. Your environment is radically different than the one my instance had. |
@goldfire Please try the latest master branch. It should resolve the problem. |
Amazing, it works! I can't thank you enough. Is there any chance that fix will make it into npm anytime soon? |
@goldfire it is available in npm now |
I might actually meet my deadline now :) Thank you very much! |
Kickass. It would be nice if we had a CI environment for a bunch of the OSes that people generally deploy node to. It would nice to know when these things break in various environments. |
It installed fine on my Macbook Pro with node v0.6.6, but when I try to deploy it fails with the following. Any ideas what could be causing this?
The text was updated successfully, but these errors were encountered: