Skip to content
This repository

Trouble building natively on Heroku #116

Closed
pselden opened this Issue March 26, 2012 · 1 comment

2 participants

Paul Selden Brian C
Paul Selden

I know this isn't exactly domain... but I was hoping someone else out there might have been having this problem.

I'm deploying on heroku and getting this error:

   > pg@0.6.16 install /tmp/build_t7ec58gz96g8/node_modules/pg
   > node-waf configure build || (exit 0)

   Checking for program g++ or c++          : /usr/bin/g++ 
   Checking for program cpp                 : /usr/bin/cpp 
   Checking for program ar                  : /usr/bin/ar 
   Checking for program ranlib              : /usr/bin/ranlib 
   Checking for g++                         : ok  
   Checking for node path                   : not found 
   Checking for node prefix                 : ok /tmp/node-node-oxaC 
   Checking for program pg_config           : /usr/bin/pg_config 
   'configure' finished successfully (0.095s)
   Waf: Entering directory `/Users/me/Documents/myapp/node_modules/pg/build'
   Waf: Leaving directory `/Users/me/Documents/myapp/node_modules/pg/build'
   Traceback (most recent call last):
     File "/tmp/node-node-oxaC/bin/node-waf", line 16, in <module>
       Scripting.prepare(t, os.getcwd(), VERSION, wafdir)
     File "/tmp/node-node-oxaC/bin/../lib/node/wafadmin/Scripting.py", line 145, in prepare
       prepare_impl(t, cwd, ver, wafdir)
     File "/tmp/node-node-oxaC/bin/../lib/node/wafadmin/Scripting.py", line 135, in prepare_impl
       main()
     File "/tmp/node-node-oxaC/bin/../lib/node/wafadmin/Scripting.py", line 188, in main
       fun(ctx)
     File "/tmp/node-node-oxaC/bin/../lib/node/wafadmin/Scripting.py", line 386, in build
       return build_impl(bld)
     File "/tmp/node-node-oxaC/bin/../lib/node/wafadmin/Scripting.py", line 405, in build_impl
       bld.compile()
     File "/tmp/node-node-oxaC/bin/../lib/node/wafadmin/Build.py", line 268, in compile
       os.chdir(self.bldnode.abspath())
   OSError: [Errno 2] No such file or directory: '/Users/me/Documents/myapp/node_modules/pg/build'

Notice that it's trying to find a directory on my local machine. I DID have my node_modules/pg checked into in git at one point, but I no longer do. Any idea what could be causing this? There's a similar issue on: npm/npm#1872... maybe we need to do a clean before?

I do have another compiled module (bcrypt) that installs successfully, but it runs this as part of its build process:

   > bcrypt@0.5.0 install /tmp/build_t7ec58gz96g8/node_modules/bcrypt
   > make build

   rm -f bcrypt_lib.node
   rm -Rf build
   node-waf configure
   Checking for program g++ or c++          : /usr/bin/g++ 
   Checking for program cpp                 : /usr/bin/cpp 
   Checking for program ar                  : /usr/bin/ar 
   Checking for program ranlib              : /usr/bin/ranlib 
   Checking for g++                         : ok  
   Checking for program gcc or cc           : /usr/bin/gcc 
   Checking for gcc                         : ok  
   Checking for node path                   : not found 
   Checking for node prefix                 : ok /tmp/node-node-oxaC 
   Checking for function RAND_bytes         : yes 
   'configure' finished successfully (0.321s)
   node-waf build
   Waf: Entering directory `/tmp/build_t7ec58gz96g8/node_modules/bcrypt/build'

Notice that it removes some files/folders first.

Thanks!

Deleted user

The content you are editing has changed. Reload the page and try again.

6 months old ticket, don't know when but this seems fixed. It works fine for me

Sending Request…

Attach images by dragging & dropping or selecting them. Octocat-spinner-32 Uploading your images… Unfortunately, we don't support that file type. Try again with a PNG, GIF, or JPG. Yowza, that's a big file. Try again with an image file smaller than 10MB. This browser doesn't support image attachments. We recommend updating to the latest Internet Explorer, Google Chrome, or Firefox. Something went really wrong, and we can't process that image. Try again.

Brian C brianc closed this December 10, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.