-
Notifications
You must be signed in to change notification settings - Fork 976
Build Error on Ubuntu/Debian with abp-filter-parser-cpp #214
Comments
I'm getting a different build error on master. Same command:
|
I am getting other errors mostly because of node command usage on Debian:
|
I think the first error for the tag can go away if you setup ssh github access. For the other error please try updating to node-gyp v3.2.1 |
There are many errors like that. I just listed one. I can list the full output if you want. |
Same problem as asiminiceanu but with Fedora 23. thanks (i can join my npm-debug-log file) |
I'm also getting the error below but it is on OSX 10.9.2... I'd delete and move this elsewhere, but I made the comment before I noticed it's about ubuntu/linux and it doesn't look like I can delete a comment. ../././filter.h:12:10: fatal error: 'BloomFilter.h' file not found npm ERR! [email protected] install: npm ERR! Please include the following file with any support request: |
The version of nodejs in Ubuntu's repositories is too old. Edit: No, that wasn't the entire problem. |
I am running node-gyp v3.2.1. Also, I can clone and compile abp-filter-parser-cpp on it's own from source here: https://github.com/bbondy/abp-filter-parser-cpp.git |
I am having a similar issue on OpenSuse Leap 42:
|
I too am seeing the error with abp-filter-parser-cpp on debian sid. node-gyp is 3.2.1 so that isn't the issue |
in #237, sid says that updating to node 5.5 fixed it. i am Away-From-Linux-Keyboard right now, but curious if that works for others. |
@diracdeltas I was still getting that with node 5.5 yesterday, but I had a host of other problems. I wound up basically removing all of my node modules & libs (things installed with -g and so on), making sure I chowned it all (I think something at some point must've been run with sudo) and various other hiccups, but ultimately I did get it working last night and ... <3 <3. I did open another issue about configuable ports - I have too many other things that all want 8080 |
I have nodejs v5.5, npm v3.5.3 and node-gyp v3.2.1 and I can't finish the npm install :s https://pastebin.mozilla.org/8857451 any solution ? |
@diracdeltas @bbondy I have the same problem to build brave on Ubuntu, I tried build with differents version of NPM and NODE, I using version V5.5.0 on NODE and V3.5.3 in NPM. |
I fixed this for me on Debian unstable by deleting |
I was also independently verifying the same steps on Ubuntu 14.04.1 x86_64 and it works with a cleared node_modules directory: node-gyp v3.2.1 |
I was able to solve this, using: sudo npm install --unsafe-perm |
@Saynt Thanks, Its work with me. |
EDIT: Nevermind, forgot to install base devel packages! Stupid me! |
@Saynt Thanks! |
Confirming that upgrading npm/node fixes the issue for Fedora 23 as well. |
On Ubuntu 15.04, built Node 5.5 per these instructions Was able to build "successfully." Can run server and tests; running browser fails with "electron: not found." Searching through log other tickets to address same. |
Hello @Saynt npm ERR! Linux 3.19.0-47-generic npm ERR! enoent ENOENT: no such file or directory, chmod '/home/shahbaz17/git/browser-laptop/node_modules/extract-zip/node_modules/mkdirp/bin/cmd.js' npm ERR! Please include the following file with any support request: |
@PunkUnity you can do a clean install by |
that works perfect for me on archlinux! Thanks! |
@shahbaz17 maybe try this: nodejs/node#2814 |
I'm still having this issue. Still getting the
error |
@Saynt not working after following nodejs/node#2814 |
Very Similar error here.
-g gives even more strange results. The rest always fails with above error |
installing with --unsafe-perms fixes this issue for me. @jmcastellote do you have bulid-essential installed? |
fixed: |
@elsehow I have tried the same things @jmcastellote did, to no avail. --unsafe-perms, and -g. Both also fail. And yes, build-essential is absolutely installed. |
Similar issue with |
Same issue with |
FYI I was able to fix it by adding an empty
|
I read somewhere that the |
For people struggling with build errors on Ubuntu 14.02, running a clean install should solve it:
|
I am getting the same error. Using OS X 10.10.5 (14F1605) . npm version : 3.7.3 |
Hi, trying to build on a Mac and having very similar problems. This is the error I'm getting: 4 errors generated. I've tried node v 5.5 as well - clearing node-modules each time and doing a full import. I was on node-gyp 3.2.1 previously - upgraded and now can't seem to get back - don't know if that's impacting anything. also tried doing npm install with --unsafe-perms - no luck there. Any help would be greatly appreciated! thanks |
I found this issue, which was the root problem: #807 I was able to get Brave to build using the fix with NPM link, but was not able to run it - found hacking it with global install of abp-parser-filter-cpp allowed me to run (woohoo!) but obviously not a good long term solution - so still interested to find out what is wrong in my environment that I can't use the abp-filter-parser from npm... |
Setting up node -v 5.5.0 node-gyp -v 3.2.1 on Ubuntu 14.04.01 x86_64 (same as #214 (comment)) and
fatal error: BloomFilter.h: No such file or directory <- Isn't it the cause of the error? |
@luixxiul had you tried a clean npm install? I'm also using Ubuntu. |
Finally succeeded. Not sure what was wrong at all (maybe due to the version of Node?). The procedure that worked on Ubuntu 14.04.01 (clean install): https://gist.github.com/luixxiul/e294f2e5ef5bdf5ab6910d8224a9b7a9 Would someone confirm this works? If it does or does not, please tell me. |
I'm getting the following git permission error when trying to
sudo npm install
from tag v0.7.7. Looks like you may just need to open it up?The text was updated successfully, but these errors were encountered: