Hi, I could send this to just T.C., but I know there are other packages that rely on nodejs-nan, so I'm sending it to the list.
After the nodejs macro updates where we can now have multiple instances of nodejs-nan installed, the packages I have that depend on nan do not recompile. It isn't a version thing, it is a Error: Cannot find module 'nan' problem.[1][2] Is there something that I need to do in my spec files to utilize (or not utilize) nan.
Troy
[1] https://kojipkgs.fedoraproject.org//work/tasks/657/6980657/build.log [2] https://kojipkgs.fedoraproject.org//work/tasks/5519/6975519/build.log
On 09/06/14 17:19, Troy Dawson wrote:
After the nodejs macro updates where we can now have multiple instances of nodejs-nan installed, the packages I have that depend on nan do not recompile. It isn't a version thing, it is a Error: Cannot find module 'nan' problem.[1][2] Is there something that I need to do in my spec files to utilize (or not utilize) nan.
You should be using "%nodejs_symlink_deps --build" to setup the environment before the build, not setting NODE_PATH to the global library directory.
Tom
On 06/09/2014 11:27 AM, Tom Hughes wrote:
On 09/06/14 17:19, Troy Dawson wrote:
After the nodejs macro updates where we can now have multiple instances of nodejs-nan installed, the packages I have that depend on nan do not recompile. It isn't a version thing, it is a Error: Cannot find module 'nan' problem.[1][2] Is there something that I need to do in my spec files to utilize (or not utilize) nan.
You should be using "%nodejs_symlink_deps --build" to setup the environment before the build, not setting NODE_PATH to the global library directory.
Tom
That wasn't it, but it got me looking in the right direction. The nodejs-nan package had a bad link, it was linking nan -> nodejs-nan@1 Which was a broken link, it needed to link to nan -> nan@1
I've got the nodejs-nan package fixed. One that makes it to the rawhide repo I can rebuild my other nodejs packages that didn't rebuild correctly.
Troy
nodejs@lists.fedoraproject.org