Open RickCogley opened 9 years ago
@RickCogley Thanks for writing this down, helped me out today with my raspberry pi project!
hi Max, glad to hear it.
On 2016 Oct 18, at 12:05, Max Bittker notifications@github.com wrote:
@RickCogley https://github.com/RickCogley Thanks for writing this down, helped me out today with my raspberry pi project!
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/flowdock/hubot-flowdock/issues/84#issuecomment-254394491, or mute the thread https://github.com/notifications/unsubscribe-auth/AAfRSCtyr5uKui_EO_NwhXxoq6TJr3NMks5q1DeXgaJpZM4GVZWl.
This email message and any attachments are confidential, and are meant to be read by the intended recipient only. If you are not the intended recipient, we would request you delete this message or any attachments without reading or distributing, and kindly advise eSolia Inc. (contacts: esolia.com/about http://esolia.com/about). Thank you in advance.
I wanted to make an issue here just to document some of the things I had to do to get this working, although everything appears to be working now.
I'm installing hubot on a Webfaction shared server, running Centos6 and had to do a few things.
After cd-ing to my webapps/hubot application folder, I had to do an
export PATH=$PWD/bin/:$PATH
to make sure bin/hubot can be found.Upgrade npm to 3.3.9 by doing:
Make sure npm uses python 2.7 by doing:
Update node-gyp:
Tell node-gyp to use python 2.7, too:
After those steps, a number of problems went away, but, it still wouldn't work fully, claiming "Failed at the buffertools@2.1.3 install script 'node-gyp rebuild'.". Confirming on both buffertools and node-gyp repos, it appears you need a more advanced gcc, than what is provided by default for Centos6, which is what Webfaction maintains by default.
So, you then setup GCC 4.8+, which is C++11-capable, per: https://community.webfaction.com/questions/14581/compiling-gcc-48
The gcc upgrade takes quite a while, so it's best to do a
screen
session and run it in that. When it is done, you can exit and re enter your terminal, trynpm upgrade
again, and voilà!, it works.