Package Details: inox-dev 72.0.3622.0-1

Git Clone URL: (read-only)
Package Base: inox-dev
Description: A web browser built for speed, simplicity, and security
Upstream URL:
Licenses: BSD
Submitter: bm456
Maintainer: bm456
Last Packager: bm456
Votes: 1
Popularity: 0.000059
First Submitted: 2017-11-07 15:58
Last Updated: 2018-12-03 01:26

Dependencies (37)

Required by (0)

Sources (97)

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

bm456 commented on 2018-02-26 02:54

as usual

clean your working directory, update your pkgbuild and all will work

eugen-b commented on 2018-02-20 13:33

This is the error message concerning desu.patch

The text leading up to this was:
|--- a/third_party/webrtc/api/audio/  2018-02-15 07:08:02.000000000 -0400
|+++ b/third_party/webrtc/api/audio/  2018-02-15 14:40:34.536836946 -0400
File to patch: 
Skip this patch? [y] 
Skipping patch.
1 out of 1 hunk ignored
==> ERROR: A failure occurred in prepare().

There is indeed no file /tmp/makepkg/inox-dev/src/chromium-66.0.3346.8/third_party/webrtc/api/audio/

eugen-b commented on 2018-02-19 13:35

That line breaks the build: + patch -Np1 -i ../desu.patch Some file isn't in place is the message, it asks to give the path to the file. Commenting this patch allows to build.

eugen-b commented on 2018-01-19 20:45

Finally I got the right idea: I deleted all *.patch files in my ~/inox-dev folder which I created with git clone aur_link and downloaded them again. Now the build works. ninja is at [2700/31314]. Sorry, that I haven't tried it earlier.

eugen-b commented on 2018-01-14 23:16

Thanks for your effort, but I get this error as before

patching file components/safe_browsing/
Hunk #1 FAILED at 65.
1 out of 1 hunk FAILED -- saving rejects to file components/safe_browsing/
==> ERROR: A failure occurred in prepare().

bm456 commented on 2018-01-13 21:02


about your bugs (thanks for alert it) :)

1)<br> i'll delete it (as i dont build widevine-eme)

2) gna its revisited and it does this (cp line its deleted)

3) revisited

4) as you didnt used gna you got a chromium bug (gna its live and i'll patches it)

about cores ninja by default uses 1.25 times your number of cores (example, if you've 8, ninja uses 10), for normal programs you'll get an advantage (ram caching), but with chromium gives troubles

more jobs = more ram (at least 1.25-1.45gb per job, for 10 jobs you'll need at least 18 gb rab)

pd, please read this (it say you how much jobs should put)

eugen-b commented on 2018-01-12 13:25

inox-dev 65.0.3315.3-5 fails on several steps of the PKGBUILD

1) original PKGBUILD

==> Starting prepare()...
sed: can't read ../chromium-widevine.patch: No such file or directory
cp: cannot stat '../synchronization_flags.h': No such file or directory
==> ERROR: A failure occurred in prepare().

2) comment that line #cp ../synchronization_flags.h base/synchronization/synchronization_flags.h

patching file components/safe_browsing/
Hunk #1 FAILED at 65.
1 out of 1 hunk FAILED -- saving rejects to file components/safe_browsing/
==> ERROR: A failure occurred in prepare().

3) It doesn't make sense for me to comment that line, but if I comment the line 312 #patch -Np1 -i ../2ke.patch

patching file chrome/service/
Hunk #1 FAILED at 55.
Hunk #2 FAILED at 68.
2 out of 2 hunks FAILED -- saving rejects to file chrome/service/
==> ERROR: A failure occurred in prepare().

4) The error is in the file gna.patch, so I comment it out in PKGBUILD # patch -Np1 -i ../gna.patch

  -> Setup  compiler
Building gn manually in a temporary directory for bootstrapping...
ninja: Entering directory `/tmp/makepkg/inox-dev/src/temp/tmp7OW22U'
[210/364] CXX base/synchronization/lock_impl_posix.o
FAILED: base/synchronization/lock_impl_posix.o
/tmp/makepkg/inox-dev/src/chromium-65.0.3315.3/third_party/llvm-build/Release+Asserts/bin/clang++ -MMD -MF base/synchronization/lock_impl_posix.o.d  -I/tmp/makepkg/inox-dev/src/temp/tmp7OW22U/gen -I/tmp/makepkg/inox-dev/src/chromium-65.0.3315.3 -march=native -mtune=native -O2 -pipe -fstack-protector-strong -Wno-unknown-warning-option -DNO_TCMALLOC -D__STDC_FORMAT_MACROS -O2 -g0 -D_FILE_OFFSET_BITS=64 -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -pthread -pipe -fno-exceptions -march=native -mtune=native -O2 -pipe -fstack-protector-strong -Wno-unknown-warning-option -std=c++14 -Wno-c++11-narrowing -c /tmp/makepkg/inox-dev/src/chromium-65.0.3315.3/base/synchronization/ -o base/synchronization/lock_impl_posix.o
/tmp/makepkg/inox-dev/src/chromium-65.0.3315.3/base/synchronization/ fatal error: 'base/synchronization/synchronization_flags.h' file not found
#include "base/synchronization/synchronization_flags.h"
1 error generated.
[215/364] CXX base/threading/platform_thread_posix.o
ninja: build stopped: subcommand failed.
Command '['ninja', '-C', '/tmp/makepkg/inox-dev/src/temp/tmp7OW22U', '-w', 'dupbuild=err', 'gn']' returned non-zero exit status 1
==> ERROR: A failure occurred in build().

eugen-b commented on 2018-01-12 11:44

Thanks for the tips! You rarely get such tips on AUR. Does the ninja -j # switch hasve anything to do with CPU cores? See I have four, maybe I should set -j 3 or -j 4? If not I should probably set -j 6 as 6 x 1.25 = 7.5 < 8GB. It is indeed becoming more difficult to build in RAM. Even if I boot too TTY.

bm456 commented on 2018-01-07 23:17


hi, its a "client" error (OOM), instead of an upstream error.

i can make you some recomendations

  • replace ninja line with your ram amount / 1.25, if you've 8 ram please use

ninja -C out/Release -j 12 -v pdf chrome chrome_sandbox chromedriver widevinecdmadapter clear_key_cdm

  • avoid make ram-epensive taks (have multiple videos open, extract tarballs) and more

  • NEVER try to build on ram (tmpfs) .. you'll get this OOM error

eugen-b commented on 2018-01-01 09:10

Build fails for 65.0.3298.3-7. Here is the terminal output of makepkg:

Here is the file

Sorry for the missspelled package name in my last bug report.