The 32-bit thing was taken care of possible in the next release. You should upgrade to a newer v0.7.x release ;)
So the dlopen() error there is that it's not the correct architecture (i.e. you built a 32-bit node, but a 64-bit module. This is a problem with node-waf; node-gyp solves this by checking `process.arch` and building for that type). So ya, try updating to one of the v0.7.x releases that will build a 64-bit binary once again. On Tue, Mar 27, 2012 at 3:21 PM, SteveCronin <[email protected]>wrote: > Cool -- I've gotten 0.7.3 (which seems to have reverted to requiring > modules to 32-bit) > So I rebuilt as 32-bit (even though I don't want to) > Now when I invoke here's the error I see (used to be unable to load shared > library): > > node.js:197 > throw e; // process.nextTick error, or 'error' event on first tick > ^ > Error: > dlopen(/Users/scronin/Documents/HSD/Node/node-XYZ/build/Release/node-XYZ.node, > 1): no suitable image found. Did find: > /Users/scronin/Documents/HSD/Node/node-XYZ/build/Release/node-XYZ.node: > mach-o, but wrong architecture > > Compiled successfully using node-waf > Still looking into getting node-gyp running... > > Thanks for all the helpful info - as always you are a treat to work with! > > > On Tuesday, March 27, 2012 5:14:57 PM UTC-5, Nathan Rajlich wrote: >> >> Is there yet another configuration setting that has to be informed as to >>> what the System Preference Network Proxy setting is? >>> >> >> Yes, and I don't think npm currently proxies the setting (though it >> probably should). You can either pass a "--proxy=my.proxy.server" switch or >> set the "HTTP_PROXY" env variable. >> >> >>> Where would this be documented? (sigh...) >>> >> >> It's currently not documented. Sorry about that! When a timeout happens >> it may good for me to display the proxy option (since that will usually be >> the problem I guess). I'm working on getting some basic man pages in there. >> >> >>> Why does it appear to be downloading a .tar.gz of the version of node >>> that is already installed? >>> >> >> node-gyp downloads the tarball of the current version so that it can >> extract the .h header files that node was compiled with, to get the closest >> match possible. This is specifically for Windows, where the .h header files >> never get installed anywhere on the system. >> >> What is the easiest way to obtain the 0.7.6 instance you mention below to >>> get to the real error... >>> >> >> How did you install previously? You can download installers or the >> tarballs for any of the versions on http://nodejs.org/dist/ >> > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
