-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
node-gyp rebuild error #2045
Comments
I doubt this is the cause of your issue but Python < 2.7.9 is a security risk and Python 2 in general is EOL. Python 3.8.1 is current. |
yeah, but 2.7 is still the default on Redhat EL... |
Can you post the |
complete output
|
In file included from ../../nan/nan_new.h:189,
from ../../nan/nan.h:222,
from ../src/deasync.cc:3:
../../nan/nan_implementation_12_inl.h: In static member function ‘static Nan::imp::FactoryBase<v8::Function>::return_t Nan::imp::Factory<v8::Function>::New(Nan::FunctionCallback, v8::Local<v8::Value>)’:
../../nan/nan_implementation_12_inl.h:105:32: error: no matching function for call to ‘v8::Function::New(v8::Isolate*&, void (&)(const v8::FunctionCallbackInfo<v8::Value>&), v8::Local<v8::Object>&)’
, obj));
^
...
In file included from /opt/rh/devtoolset-8/root/usr/include/c++/8/cassert:44,
from /root/.cache/node-gyp/12.15.0/include/node/node_object_wrap.h:26,
from ../../nan/nan.h:54,
from ../src/deasync.cc:3:
../../nan/nan_object_wrap.h: In destructor ‘virtual Nan::ObjectWrap::~ObjectWrap()’:
../../nan/nan_object_wrap.h:24:25: error: ‘class Nan::Persistent<v8::Object>’ has no member named ‘IsNearDeath’
assert(persistent().IsNearDeath());
^~~~~~~~~~~ These indicate the version of |
updated node-gyp, deasync and nan, but the error persists
|
This shows that the latest |
In my-case it was failing on Linux-mint 19.2, for some reasons on run-time gcc++ was not accessible. build-essential package is a reference for all the packages needed to compile a Debian packages. It generally includes the GCC/g++ compilers and libraries and some other utilities. Informational for list of build-essential packages can be found on build-essentials |
this is already resolved...node version was to new |
Verbose output (from npm or node-gyp):
The text was updated successfully, but these errors were encountered: