Discover what is breaking binary based packages on some dev/pro machines #441

Martii · 2014-11-23T12:08:56Z

Since this is specific currently to @Zren but can apply to others if they are having any issue with their system... only those having issues need apply themselves.

Please post results of the following:

Platform with full version information e.g. if Windows which one.. if Linux which one... if Mac OSX which one
$ npm -v
$ node -v
$ npm install express-minify
Any other useful information

See related:

Installing 1.2.1 error on debian wheezy (Error: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found) sass/node-sass#517

The text was updated successfully, but these errors were encountered:

Martii · 2014-11-23T12:22:47Z

Zren commented on Nov 23, 2014, 3:31 AM EST:

99% sure it works for you because you have npm 2.x

Nope... I will do a test with npm 1.4.28 ~~momentarily~~ but I suspect it will work okay here on this Nix distro as it did on Ubuntu

Martii · 2014-11-23T20:27:31Z

A Mac OSX test result (migration specificially) from someone else with a similar issue with node-sass which is a dep in express-minify.

PMK commented on Nov 23, 2014, 8:44 AM EST:

Edit:
Thanks to sass/node-sass-binaries@9d6417d#commitcomment-8683794 I switched to node 0.10.33 and solves the problem.

Zren · 2014-11-23T22:37:46Z

#431 (comment)

Looks like I will be putting express-minify in optionalDependancies as node-sass does not build on heroku (linux-x64 / Node 0.10.33 / NPM 1.4.28) either.

Try again.

Martii · 2014-11-23T22:56:33Z

If you don't put your dev stats in from above... as to why you are having issues with your machine any related issue/pr will be closed with invalid label. e.g. express-minify won't be optional anymore with the try..catch and you won't be able to dev... please put those in here and work with the project instead of against it.

Martii · 2014-11-23T22:57:18Z

One of my results:

Ubuntu 14.04.1 LTS (64 bit desktop)

$ node -v
v0.10.34-pre

$ npm -v
1.4.28

$ npm install node-sass
/
> node-sass@1.2.3 install /home/user/node_modules/node-sass
> node scripts/install.js

Binary downloaded and installed at /home/user/node_modules/node-sass/vendor/linux-x64/binding.node

> node-sass@1.2.3 postinstall /home/user/node_modules/node-sass
> node scripts/build.js

`linux-x64` exists; testing
Binary is fine; exiting
node-sass@1.2.3 ../node_modules/node-sass
├── get-stdin@3.0.2
├── object-assign@1.0.0
├── replace-ext@0.0.1
├── cross-spawn@0.2.3 (lru-cache@2.5.0)
├── mkdirp@0.5.0 (minimist@0.0.8)
├── shelljs@0.3.0
├── nan@1.4.1
├── chalk@0.5.1 (escape-string-regexp@1.0.2, ansi-styles@1.1.0, supports-color@0.2.0, has-ansi@0.1.0, strip-ansi@0.3.0)
├── meow@2.0.0 (minimist@1.1.0, camelcase-keys@1.0.0, indent-string@1.2.0)
├── gaze@0.5.1 (globule@0.1.0)
├── mocha@2.0.1 (escape-string-regexp@1.0.2, diff@1.0.8, growl@1.8.1, commander@2.3.0, glob@3.2.3, debug@2.0.0, jade@0.26.3)
└── request@2.48.0 (caseless@0.7.0, json-stringify-safe@5.0.0, aws-sign2@0.5.0, forever-agent@0.5.2, stringstream@0.0.4, oauth-sign@0.5.0, tunnel-agent@0.4.0, node-uuid@1.4.1, qs@2.3.3, mime-types@1.0.2, combined-stream@0.0.7, form-data@0.1.4, bl@0.9.3, tough-cookie@0.12.1, http-signature@0.10.0, hawk@1.1.1)

And another...

ROSA 2014.1 Fresh (64 bit R4)

$ node -v
v0.10.33

$ npm -v
1.4.28

$ echo Same success result as below updated npm install for express-minify

$ sudo npm install npm -g

$ npm -v
2.1.9

$ npm install express-minify
|
> node-sass@1.2.3 install /home/user/tmp/nodestuff/node_modules/express-minify/node_modules/node-sass
> node scripts/install.js

Binary downloaded and installed at /home/user/tmp/nodestuff/node_modules/express-minify/node_modules/node-sass/vendor/linux-x64/binding.node                                                                            

> node-sass@1.2.3 postinstall /home/user/tmp/nodestuff/node_modules/express-minify/node_modules/node-sass   
> node scripts/build.js                                                                                     

`linux-x64` exists; testing                                                                                 
Binary is fine; exiting                                                                                     
express-minify@0.1.1 node_modules/express-minify                                                            
├── on-headers@1.0.0                                                                                        
├── cssmin@0.4.2                                                                                            
├── coffee-script@1.8.0 (mkdirp@0.3.5)                                                                      
├── uglify-js@2.4.15 (uglify-to-browserify@1.0.2, async@0.2.10, source-map@0.1.34, optimist@0.3.7)          
├── stylus@0.49.3 (css-parse@1.7.0, mkdirp@0.3.5, sax@0.5.8, source-map@0.1.40, debug@2.1.0, glob@3.2.11)   
├── less@2.1.0 (graceful-fs@3.0.4, mime@1.2.11, source-map@0.1.40, mkdirp@0.5.0, promise@6.0.1, request@2.48.0)                                                                                                         
└── node-sass@1.2.3 (get-stdin@3.0.2, object-assign@1.0.0, replace-ext@0.0.1, cross-spawn@0.2.3, mkdirp@0.5.0, shelljs@0.3.0, nan@1.4.1, chalk@0.5.1, request@2.48.0, gaze@0.5.1, mocha@2.0.1, meow@2.0.0)

Zren · 2014-11-23T23:02:58Z

Ubuntu 10.04.4 LTS

Admin@ADMIN-PC ~/Code/Git/OpenUserJS.org (pd4)     
$ heroku run bash                                             
Running `bash` attached to terminal... up, run.5342
~ $ node -v
node -v
v0.10.33
~ $ npm -v
npm -v
1.4.28
~ $ lsb_release -a
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 10.04.4 LTS
Release:        10.04
Codename:       lucid
~ $ npm install node-sass
npm install node-sass
npm WARN package.json mu2@0.5.20 No repository field.
npm WARN package.json bootstrap-markdown@2.7.0 'repositories' (plural) Not supported. Please pick one as the 'repository' field
-
> node-sass@1.2.3 install /app/node_modules/node-sass
> node scripts/install.js

Binary downloaded and installed at /app/node_modules/node-sass/vendor/linux-x64/binding.node

> node-sass@1.2.3 postinstall /app/node_modules/node-sass
> node scripts/build.js

`linux-x64` exists; testing

module.js:356
  Module._extensions[extension](this, filename);
                               ^
Error: /usr/lib/libstdc++.so.6: version `CXXABI_1.3.5' not found (required by /app/node_modules/node-sass/vendor/linux-x64/binding.node)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/app/node_modules/node-sass/lib/index.js:181:15)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)

npm ERR! node-sass@1.2.3 postinstall: `node scripts/build.js`
npm ERR! Exit status 8
npm ERR!
npm ERR! Failed at the node-sass@1.2.3 postinstall script.
npm ERR! This is most likely a problem with the node-sass package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node scripts/build.js
npm ERR! You can get their info via:
npm ERR!     npm owner ls node-sass
npm ERR! There is likely additional logging output above.
npm ERR! System Linux 3.8.11-ec2
npm ERR! command "/app/vendor/node/bin/node" "/app/vendor/node/bin/npm" "install" "node-sass"
npm ERR! cwd /app
npm ERR! node -v v0.10.33
npm ERR! npm -v 1.4.28
npm ERR! code ELIFECYCLE
npm ERR! not ok code 0

Martii · 2014-11-23T23:24:54Z

So is that 32 bit or 64 bit? Ubuntu has "server" release only for that back in 2012.

Zren · 2014-11-23T23:39:14Z

Fixed Heroku by updating to a newer stack. The ceder stack was deprecated, and the ceder-14 must have whatever libraries sass needs.

https://devcenter.heroku.com/articles/stack

Martii · 2014-11-24T00:27:08Z

So are you okay to go with express-minify from a standard package installation standpoint with your stack upgrade?

Zren · 2014-11-24T00:48:31Z

We don't need to put express-minify in optionalDependencies to be able to push to staging servers at Heroku. We do need to continue treating it as an optional module however until I fix it locally. I'd personally move it to optionalDependencies anyways just to label it as such but it's not necessary so long as the project's code treats it as such.

Martii · 2014-11-24T01:19:47Z

The problem lays with LESS/SASS support... when bootswatch gets compiled run-time that will be the first thing... we are already prepping for the host support on this... I can possibly add it as a separate dependency since node caches but I'd rather just use it since it has that support and it's one less dep... so you'll need to move toward that goal as well. Like I said I've held off on this but it's coming up.

Zren · 2014-11-24T01:28:18Z

The problem lays with LESS/SASS support

Bootswatch is LESS. SASS is the dependency that breaks. LESS all is sunshine and rainbows. Remember I'm the one who first compiled our bootswatch theme in the first place.

So no foreseeable problems with that.

Martii · 2014-11-24T01:32:51Z

Remember I'm the one who first compiled our bootswatch theme in the first place.

Yes I recall quite well the months later your notification that it was a compiled file which someone put sizzles fave font into. And if you want to move forward with research (assuming you need this) express-minify handles this... so you have to get it (express-minify) working for your personal hosting of the production build and dev.

Anyhow I'm not going to take any more time on this particular right now because I have other duties to perform as well... just keep it in mind on the back burner.

Martii · 2014-11-24T02:20:36Z

Renamed this for long term issue usage... still a milestone with an indefinite date of closure.

Martii · 2015-01-22T08:22:07Z

@Zren
Are you still getting this? The only error I get on pro is that a SunOS binary from sass isn't available to be downloaded:

Can not download file from https://raw.githubusercontent.com/sass/node-sass-binaries/v1.2.3/sunos-x64/binding.node

... but it has made zero difference on production running... because we don't use SASS currently even in express-minify e.g. it installs here locally on my devs, installs on pro and I tested your dev site out with a specific request and it is minifying CSS so express-minify appears to not be the culprit for you.

Martii · 2015-10-30T10:00:59Z

Misc ref:

Failing when using Node 4.0.0 jdesboeufs/connect-mongo#194 (comment) with kerberos via connect-mongo ERR on Linux boxes... install the OS dep with whatever package manager you use.

Example:

$ sudo apt-get install libkrb5-dev

... this will flip the ERR in gyp to nothing or just warnings. Some 64 bit distros require lib64krb5-devel e.g. install the developer library not just the runtime library. This ERR is usually non-fatal on Linux boxes but kind of disrupting to see.

From this (clipped):

$ npm install

> kerberos@0.0.17 install /home/user/repo/git/OpenUserJS.org/martii/OpenUserJS.org/node_modules/kerberos
> (node-gyp rebuild) || (exit 0)

make: Entering directory '/home/user/repo/git/OpenUserJS.org/martii/OpenUserJS.org/node_modules/kerberos/build'
  CXX(target) Release/obj.target/kerberos/lib/kerberos.o
In file included from ../lib/kerberos.cc:1:0:
../lib/kerberos.h:5:27: fatal error: gssapi/gssapi.h: No such file or directory
 #include <gssapi/gssapi.h>
                           ^
compilation terminated.
kerberos.target.mk:94: recipe for target 'Release/obj.target/kerberos/lib/kerberos.o' failed
make: *** [Release/obj.target/kerberos/lib/kerberos.o] Error 1
make: Leaving directory '/home/user/repo/git/OpenUserJS.org/martii/OpenUserJS.org/node_modules/kerberos/build'
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:270:23)
gyp ERR! stack     at emitTwo (events.js:87:13)
gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
gyp ERR! System Linux 3.14.53-nrj-desktop-1rosa-x86_64
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/user/repo/git/OpenUserJS.org/martii/OpenUserJS.org/node_modules/kerberos
gyp ERR! node -v v4.2.1
gyp ERR! node-gyp -v v3.0.3
gyp ERR! not ok 

> kerberos@0.0.17 install /home/user/repo/git/OpenUserJS.org/martii/OpenUserJS.org/node_modules/kerberos
> (node-gyp rebuild) || (exit 0)

make: Entering directory '/home/user/repo/git/OpenUserJS.org/martii/OpenUserJS.org/node_modules/kerberos/build'
  CXX(target) Release/obj.target/kerberos/lib/kerberos.o
In file included from ../lib/kerberos.cc:1:0:
../lib/kerberos.h:5:27: fatal error: gssapi/gssapi.h: No such file or directory
 #include <gssapi/gssapi.h>
                           ^
compilation terminated.
kerberos.target.mk:94: recipe for target 'Release/obj.target/kerberos/lib/kerberos.o' failed
make: *** [Release/obj.target/kerberos/lib/kerberos.o] Error 1
make: Leaving directory '/home/user/repo/git/OpenUserJS.org/martii/OpenUserJS.org/node_modules/kerberos/build'
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:270:23)
gyp ERR! stack     at emitTwo (events.js:87:13)
gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
gyp ERR! System Linux 3.14.53-nrj-desktop-1rosa-x86_64
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/user/repo/git/OpenUserJS.org/martii/OpenUserJS.org/node_modules/kerberos
gyp ERR! node -v v4.2.1
gyp ERR! node-gyp -v v3.0.3
gyp ERR! not ok 

> OpenUserJS.org@0.2.1 postinstall /home/user/repo/git/OpenUserJS.org/martii/OpenUserJS.org
> node dev/init.js

Checking project dependencies. Please wait...

... to this (clipped):

$ npm install

> kerberos@0.0.17 install /home/user/repo/git/OpenUserJS.org/martii/OpenUserJS.org/node_modules/kerberos
> (node-gyp rebuild) || (exit 0)

make: Entering directory '/home/user/repo/git/OpenUserJS.org/martii/OpenUserJS.org/node_modules/kerberos/build'
  CXX(target) Release/obj.target/kerberos/lib/kerberos.o
  CXX(target) Release/obj.target/kerberos/lib/worker.o
  CC(target) Release/obj.target/kerberos/lib/kerberosgss.o
../lib/kerberosgss.c:36:0: warning: ignoring #pragma clang diagnostic [-Wunknown-pragmas]
 #pragma clang diagnostic push
 ^
../lib/kerberosgss.c:37:0: warning: ignoring #pragma clang diagnostic [-Wunknown-pragmas]
 #pragma clang diagnostic ignored "-Wdeprecated-declarations"
 ^
../lib/kerberosgss.c: In function ‘authenticate_gss_client_wrap’:
../lib/kerberosgss.c:362:19: warning: variable ‘server_conf_flags’ set but not used [-Wunused-but-set-variable]
   char buf[4096], server_conf_flags;
                   ^
../lib/kerberosgss.c: At top level:
../lib/kerberosgss.c:930:0: warning: ignoring #pragma clang diagnostic [-Wunknown-pragmas]
 #pragma clang diagnostic pop
 ^
  CC(target) Release/obj.target/kerberos/lib/base64.o
  CXX(target) Release/obj.target/kerberos/lib/kerberos_context.o
  SOLINK_MODULE(target) Release/obj.target/kerberos.node
  COPY Release/kerberos.node
make: Leaving directory '/home/user/repo/git/OpenUserJS.org/martii/OpenUserJS.org/node_modules/kerberos/build'

> OpenUserJS.org@0.2.1 postinstall /home/user/repo/git/OpenUserJS.org/martii/OpenUserJS.org
> node dev/init.js

Checking project dependencies. Please wait...

Martii · 2016-11-01T19:09:57Z

Closing as stale

Martii self-assigned this Nov 23, 2014

Martii added the team biz This is similar to a meta discussion. label Nov 23, 2014

Martii mentioned this issue Nov 23, 2014

Implement #81 Sync Script.about with Github webhook #440

Closed

Martii changed the title ~~Discover what is breaking *express-minify* on some dev machines~~ Discover what is breaking binary based packages on some dev machines Nov 24, 2014

Martii added this to the #441 milestone Nov 24, 2014

Martii mentioned this issue May 22, 2015

Some dep updates #631

Merged

Martii changed the title ~~Discover what is breaking binary based packages on some dev machines~~ Discover what is breaking binary based packages on some dev/pro machines Oct 21, 2015

Martii added the stale Outdated. label Nov 1, 2016

Martii closed this as completed Nov 1, 2016

Martii removed their assignment Nov 1, 2016

OpenUserJS locked as resolved and limited conversation to collaborators Apr 12, 2021

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Discover what is breaking binary based packages on some dev/pro machines #441

Discover what is breaking binary based packages on some dev/pro machines #441

Martii commented Nov 23, 2014

Martii commented Nov 23, 2014

Martii commented Nov 23, 2014

Zren commented Nov 23, 2014

Martii commented Nov 23, 2014

Martii commented Nov 23, 2014

Zren commented Nov 23, 2014

Martii commented Nov 23, 2014

Zren commented Nov 23, 2014

Martii commented Nov 24, 2014

Zren commented Nov 24, 2014

Martii commented Nov 24, 2014

Zren commented Nov 24, 2014

Martii commented Nov 24, 2014

Martii commented Nov 24, 2014

Martii commented Jan 22, 2015

Martii commented Oct 30, 2015

Martii commented Nov 1, 2016

Discover what is breaking binary based packages on some dev/pro machines #441

Discover what is breaking binary based packages on some dev/pro machines #441

Comments

Martii commented Nov 23, 2014

Martii commented Nov 23, 2014

Martii commented Nov 23, 2014

Zren commented Nov 23, 2014

Martii commented Nov 23, 2014

Martii commented Nov 23, 2014

Zren commented Nov 23, 2014

Martii commented Nov 23, 2014

Zren commented Nov 23, 2014

Martii commented Nov 24, 2014

Zren commented Nov 24, 2014

Martii commented Nov 24, 2014

Zren commented Nov 24, 2014

Martii commented Nov 24, 2014

Martii commented Nov 24, 2014

Martii commented Jan 22, 2015

Martii commented Oct 30, 2015

Martii commented Nov 1, 2016