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

Installation in node 0.12.2 fails (OS X) #24

Open
hdn8 opened this issue Apr 13, 2015 · 7 comments
Open

Installation in node 0.12.2 fails (OS X) #24

hdn8 opened this issue Apr 13, 2015 · 7 comments

Comments

@hdn8
Copy link

hdn8 commented Apr 13, 2015

Failed during nodegyp rebuild:

make: *** [Release/obj.target/base64/base64.o] Error 1
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:269:23)
gyp ERR! stack     at ChildProcess.emit (events.js:110:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:1074:12)
gyp ERR! System Darwin 14.1.1
gyp ERR! command "node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/[redacted]/node_modules/base64
gyp ERR! node -v v0.12.2
gyp ERR! node-gyp -v v1.0.3
gyp ERR! not ok 
npm ERR! Darwin 14.1.1
npm ERR! argv "node" "/usr/local/bin/npm" "install"
npm ERR! node v0.12.2
npm ERR! npm  v2.7.4
npm ERR! code ELIFECYCLE

npm ERR! base64@2.1.0 install: `node-gyp rebuild`
npm ERR! Exit status 1

After reverting to node v0.10.38 the install worked fine.

@rebelliard
Copy link

  • OS X Mavericks.
  • NPM 2.9.1
  • Node 0.12.2
$ npm install --save-dev base64
\
> base64@2.1.0 install /Users/rafael/code/app/node_modules/base64
> node-gyp rebuild

  CXX(target) Release/obj.target/base64/base64.o
../base64.cc:13:17: error: calling a protected constructor of class 'v8::HandleScope'
    HandleScope scope;
                ^
/Users/rafael/.node-gyp/0.12.2/deps/v8/include/v8.h:816:13: note: declared protected here
  V8_INLINE HandleScope() {}
            ^
../base64.cc:14:52: error: no member named 'New' in 'v8::String'
    return ThrowException(Exception::Error(String::New(msg)));
                                           ~~~~~~~~^
../base64.cc:122:29: error: unknown type name 'Arguments'; did you mean 'v8::internal::Arguments'?
base64_encode_binding(const Arguments &args)
                            ^~~~~~~~~
                            v8::internal::Arguments
/Users/rafael/.node-gyp/0.12.2/deps/v8/include/v8.h:127:7: note: 'v8::internal::Arguments' declared
      here
class Arguments;
      ^
../base64.cc:124:17: error: calling a protected constructor of class 'v8::HandleScope'
    HandleScope scope;
                ^
/Users/rafael/.node-gyp/0.12.2/deps/v8/include/v8.h:816:13: note: declared protected here
  V8_INLINE HandleScope() {}
            ^
../base64.cc:127:13: error: member access into incomplete type 'const v8::internal::Arguments'
    if (args.Length() != 1)
            ^
/Users/rafael/.node-gyp/0.12.2/deps/v8/include/v8.h:127:7: note: forward declaration of
      'v8::internal::Arguments'
class Arguments;
      ^
../base64.cc:130:33: error: type 'const v8::internal::Arguments' does not provide a subscript
      operator
    if (Buffer::HasInstance(args[0])) {
                            ~~~~^~
../base64.cc:131:45: error: type 'const v8::internal::Arguments' does not provide a subscript
      operator
        v8::Handle<v8::Object> buffer = args[0]->ToObject();
                                        ~~~~^~
../base64.cc:137:18: error: type 'const v8::internal::Arguments' does not provide a subscript
      operator
    else if (args[0]->IsString()) {
             ~~~~^~
../base64.cc:138:38: error: type 'const v8::internal::Arguments' does not provide a subscript
      operator
        String::Utf8Value v8str (args[0]->ToString());
                                 ~~~~^~
../base64.cc:144:33: error: no member named 'New' in 'v8::String'
    Local<String> ret = String::New(str);
                        ~~~~~~~~^
../base64.cc:146:18: error: no member named 'Close' in 'v8::HandleScope'
    return scope.Close(ret);
           ~~~~~ ^
../base64.cc:150:29: error: unknown type name 'Arguments'; did you mean 'v8::internal::Arguments'?
base64_decode_binding(const Arguments &args)
                            ^~~~~~~~~
                            v8::internal::Arguments
/Users/rafael/.node-gyp/0.12.2/deps/v8/include/v8.h:127:7: note: 'v8::internal::Arguments' declared
      here
class Arguments;
      ^
../base64.cc:152:17: error: calling a protected constructor of class 'v8::HandleScope'
    HandleScope scope;
                ^
/Users/rafael/.node-gyp/0.12.2/deps/v8/include/v8.h:816:13: note: declared protected here
  V8_INLINE HandleScope() {}
            ^
../base64.cc:155:13: error: member access into incomplete type 'const v8::internal::Arguments'
    if (args.Length() < 1)
            ^
/Users/rafael/.node-gyp/0.12.2/deps/v8/include/v8.h:127:7: note: forward declaration of
      'v8::internal::Arguments'
class Arguments;
      ^
../base64.cc:160:33: error: type 'const v8::internal::Arguments' does not provide a subscript
      operator
    if (Buffer::HasInstance(args[0])) { // buffer
                            ~~~~^~
../base64.cc:161:45: error: type 'const v8::internal::Arguments' does not provide a subscript
      operator
        v8::Handle<v8::Object> buffer = args[0]->ToObject();
                                        ~~~~^~
../base64.cc:170:17: error: no member named 'AsciiValue' in 'v8::String'
        String::AsciiValue b64data(args[0]->ToString());
        ~~~~~~~~^
../base64.cc:171:34: error: use of undeclared identifier 'b64data'
        decoded = base64_decode(*b64data, b64data.length(), &outlen);
                                 ^
../base64.cc:174:13: error: member access into incomplete type 'const v8::internal::Arguments'
    if (args.Length() > 1 && args[1]->IsString()) {
            ^
/Users/rafael/.node-gyp/0.12.2/deps/v8/include/v8.h:127:7: note: forward declaration of
      'v8::internal::Arguments'
class Arguments;
      ^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
make: *** [Release/obj.target/base64/base64.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:269:23)
gyp ERR! stack     at ChildProcess.emit (events.js:110:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:1074:12)
gyp ERR! System Darwin 13.4.0
gyp ERR! command "node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/rafael/code/app/node_modules/base64
gyp ERR! node -v v0.12.2
gyp ERR! node-gyp -v v1.0.3
gyp ERR! not ok
npm ERR! Darwin 13.4.0
npm ERR! argv "node" "/usr/local/bin/npm" "install" "--save-dev" "base64"
npm ERR! node v0.12.2
npm ERR! npm  v2.9.1
npm ERR! code ELIFECYCLE

npm ERR! base64@2.1.0 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the base64@2.1.0 install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the base64 package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls base64
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/rafael/code/app/npm-debug.log

@poliveira89
Copy link

This occurs with me as well. 👍

Nodejs: 0.12.2
NPM: 2.7.5

Tried to install 2.1.0 version of this module.

@brandonweiss
Copy link

Same. Had to revert to an older version of Node.

@mienaikoe
Copy link

Same Issue for me

@somerandomsequence
Copy link

Me too.

@afrantz
Copy link

afrantz commented Jul 20, 2015

As the author said in the readme.txt : "this module may no longer be necessary as nodejs includes its own base64 encoding/decoding functions"

Look here to use Node.js's functions : http://stackoverflow.com/a/6182519

@prasanth-cubettech
Copy link

I have resolved this issue by using older version of node v0.10.40

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants