-
Notifications
You must be signed in to change notification settings - Fork 122
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 #35
Comments
@hitchcott thanks for reporting this! What OS are you using and what version of node are you using? |
@hitchcott secondly can you run?
|
@wanderer I think your commands above work, but I had to make a few modifications for OS X. Here's what I ran:
The install logs are here. Looks fine to me! (just warnings): |
thanks @tcoulter . So looks like the has_lib.sh script is giving a false positive for OS X. Can you tell me what the script ./utils/has_lib.sh gmpxx returns? |
|
@tcoulter what does |
|
@hitchcott can you please try install the latest version of secp256k1? Let me know what happens! thanks. |
Deleted my previous comment (didn't realize you had submodules).
On OS X, I get the following error because it can't find
|
@taoeffect @hitchcott |
Guessing you didn't see my latest comment. :) I also fixed the header problem by adding
|
so it shouldn't be using |
This:
|
I don't understand why gmp is being disabled on a mac if it's installed... |
becuase all of the build fails on mac's seem to revolve around the ./has_lib.sh script incorrectly detecting gmp. So I thought I would just disable it for macs until I can figure out a good way to detect if a library is installed |
I kinda fixed it:
Summary of changes
'OS=="mac"', {
"defines": [
"HAVE_LIBGMP=0",
"USE_NUM_GMP=0",
"USE_FIELD_INV_NUM=0",
"USE_SCALAR_INV_NUM=0"
],
"libraries": [
"-L/usr/local/lib"
]
}], EDIT: actually, removing the More elegant fix needed, and warnings should be fixed as well. Also, replacing |
Your
|
Note: The |
Also, since GMP works fine on OS X, you should remove the
|
thanks a bunch @taoeffect ! this is great. The remaining warnings should be taken care of by these flags I don't see the on linux. so maybe the flag is slightly different |
@wanderer Awesome, glad I could help. 😄 Do you think we can expect to see a new release soon? I ask because Embark is currently broken on OS X until this is fixed: embarklabs/embark#99 |
sure! @taoeffect do you mind send in a PR? I'll publish as a i get it |
@wanderer Sure, but what's the fix for the |
ok 1.1.5 is up on npm |
see embarklabs/embark#99
Here is the output of
npm install [email protected] -g
:The text was updated successfully, but these errors were encountered: