Code Monkey home page Code Monkey logo

electron-overlay's Introduction

Gentoo Overlay for Electron and some Electron-based apps

Installation

layman -a electron

electron-overlay's People

Contributors

alyst avatar brhenc avatar elprans avatar floppym avatar oczkers avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar

electron-overlay's Issues

New dev-util/gn has slot conflict with Electron

Chromium 83 requires a newer GN. I imagine Electron can work with the new one? Or perhaps a newer Electron can.

!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:

dev-util/gn:0

  (dev-util/gn-0.1463:0/0::gentoo, ebuild scheduled for merge) USE="" ABI_X86="(64)" pulled in by
    <dev-util/gn-0.1583 required by (dev-util/electron-6.1.6-r1:6.1/6.1::atom, ebuild scheduled for merge) USE="clan
g cups proprietary-codecs suid system-ffmpeg system-icu tcmalloc -component-build -custom-cflags -gconf -gnome-keyri
ng -jumbo-build -kerberos -lto -pic -pulseaudio (-selinux) -system-libvpx" ABI_X86="(64)" L10N="en-GB ja ko zh-CN zh
-TW -am -ar -bg -bn -ca -cs -da -de -el -es -es-419 -et -fa -fi -fil -fr -gu -he -hi -hr -hu -id -it -kn -lt -lv -ml
 -mr -ms -nb -nl -pl -pt-BR -pt-PT -ro -ru -sk -sl -sr -sv -sw -ta -te -th -tr -uk -vi"
    ^            ^^^^^^

  (dev-util/gn-0.1726:0/0::gentoo, installed) USE="vim-syntax" ABI_X86="(64)" pulled in by
    >=dev-util/gn-0.1726 required by (www-client/chromium-83.0.4103.23:0/0::gentoo, installed) USE="closure-compile
cups hangouts (pic) proprietary-codecs suid system-ffmpeg tcmalloc widevine -component-build -custom-cflags -kerbero
s -pulseaudio (-selinux) (-system-icu) (-system-libvpx)" ABI_X86="(64)" L10N="en-GB ja ko zh-CN zh-TW -am -ar -bg -b
n -ca -cs -da -de -el -es -es-419 -et -fa -fi -fil -fr -gu -he -hi -hr -hu -id -it -kn -lt -lv -ml -mr -ms -nb -nl -
pl -pt-BR -pt-PT -ro -ru -sk -sl -sr -sv -sw -ta -te -th -tr -uk -vi"
    ^^            ^^^^^^

electron-3.1.8: fails to build; no member named "width"

build.log

Perhaps a libvpx compatibility issue:

../../third_party/webrtc/modules/video_coding/codecs/vp9/vp9_impl.cc:720:25: error: no member named 'height' in 'vpx_codec_cx_pkt::(anonymous struct at /usr/include/vpx/vpx_encoder.h:173:5)'
pkt->data.frame.height[layer_id.spatial_layer_id];
~~~~~~~~~~~~~~~ ^
../../third_party/webrtc/modules/video_coding/codecs/vp9/vp9_impl.cc:722:25: error: no member named 'width' in 'vpx_codec_cx_pkt::(anonymous struct at /usr/include/vpx/vpx_encoder.h:173:5)'
pkt->data.frame.width[layer_id.spatial_layer_id];
~~~~~~~~~~~~~~~ ^
2 errors generated.

I am on libvpx 1.7.0 and I cannot upgrade because of Firefox:

WARNING: One or more updates/rebuilds have been skipped due to a dependency conflict:
media-libs/libvpx:0
(media-libs/libvpx-1.8.0-r1:0/6::gentoo, ebuild scheduled for merge) conflicts with
>=media-libs/libvpx-1.7.0:0/5=[postproc] required by (www-client/firefox-66.0.3:0/0::gentoo, installed)
^^^^^
<media-libs/libvpx-1.8:0=[postproc] required by (www-client/firefox-66.0.3:0/0::gentoo, installed)
^                  ^^^
<media-libs/libvpx-1.8:0/5=[postproc] required by (www-client/firefox-66.0.3:0/0::gentoo, installed)

the electron does not build

the electron does not build with ffmpeg-4 (the decision: to turn off the flag system-ffmpeg) or openssl-1.1.0. the logs are not preserved(

electron-1.7.8-vendor-libchromiumcontent.patch needs to be updated

There are many changes in libchromiumcontent/script/create-dist.

Also, there's a new dependency on ninja_syntax. At least, for that part I can help with this ebuild:

dev-python/ninja_syntax/ninja_syntax-1.7.2.ebuild

# Copyright 1999-2017 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2

EAPI=6

PYTHON_COMPAT=( python2_7 python3_{4,5,6} pypy )

inherit distutils-r1

DESCRIPTION="Python module for generating .ninja files"
HOMEPAGE="https://github.com/ninja-build/ninja"
SRC_URI="mirror://pypi/${PN:0:1}/${PN}/${P}.tar.gz"

SLOT="0"
LICENSE="Apache-2.0"
KEYWORDS="amd64 x86 ~amd64-linux ~x86-linux"

DEPEND="dev-python/setuptools[${PYTHON_USEDEP}]"

But I'm not sure if it's worth adding another dependency just for that tiny part.

Cheers!

VSCode 1.54.1 released

From Mac, about Code:

Version: 1.54.1
Commit: f30a9b73e8ffc278e71575118b6bf568f04587c8
Date: 2021-03-04T22:42:18.719Z (14 hrs ago)
Electron: 11.3.0
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: 8.7.220.31-electron.0
OS: Darwin x64 20.3.0

Strange conflicts with ICU 69 and Clang 12

I have an ~amd64 machine.

A few days ago ICU 69.1 was put on the main tree and for some reason your Electron ebuild was blocking it. It was the only package that did so on my machine.

What I did was build with -system-icu, which makes Electron crash:

 $ /usr/lib64/electron-11.2/electron
[77505:0511/161814.313653:FATAL:content_main_delegate.cc(35)] Check failed: false.
#0 0x561bde65b829 <unknown>
#1 0x561bde5d7993 <unknown>
#2 0x561bde5eaa6f <unknown>
#3 0x561bde5eb2be <unknown>
#4 0x561bdc3fe075 <unknown>
#5 0x561bdd87a6dd <unknown>
#6 0x561bdcd088b2 <unknown>
#7 0x561bdc1847b9 <unknown>
#8 0x7f69a21c37fd __libc_start_main
#9 0x561bdbe9006a _start

Aborted (core dumped)

Now after updating everything and rebuilding everything against ICU 69, I can finally update Electron to use ICU 69:

Calculating dependencies... done!
[ebuild     UD ] sys-devel/lld-11.1.0-r1::gentoo [12.0.0::gentoo] USE="-test" 0 KiB
[ebuild   R    ] dev-util/electron-11.2.3:11.2::electron  USE="clang cups js-type-check lto proprietary-codecs pulseaudio suid system-ffmpeg system-icu* tcmalloc vaapi -component-build -custom-cflags -headless -kerberos -pic (-selinux) -wayland" L10N="en-GB -am -ar -bg -bn -ca -cs -da -de -el -es -es-419 -et -fa -fi -fil -fr -gu -he -hi -hr -hu -id -it -ja -kn -ko -lt -lv -ml -mr -ms -nb -nl -pl -pt-BR -pt-PT -ro -ru -sk -sl -sr -sv -sw -ta -te -th -tr -uk -vi -zh-CN -zh-TW" 0 KiB

However, note the downgrade on LLD. What I have to do now is uninstall Clang 12 so Clang 11 becomes the default. Mismatching LLD and Clang causes a build failure. I have not yet tried building against ICU 69. Will do so shortly.

Is there any way this can be resolved so workarounds are not needed?

dev-util/electron-1.7.13 need depend on media-libs/libvpx-1.7.0

dev-util/electron-1.7.13 fails compilation with <media-libs/libvpx-1.7.0.

In file included from /usr/include/vpx/vp8.h:33:0,
                 from /usr/include/vpx/vp8cx.h:18,
                 from ../../third_party/webrtc/modules/video_coding/codecs/vp9/vp9_impl.h:21,
                 from ../../third_party/webrtc/modules/video_coding/codecs/vp9/vp9_impl.cc:12:
../../third_party/webrtc/modules/video_coding/codecs/vp9/vp9_impl.cc: In member function ‘virtual int webrtc::VP9DecoderImpl::Decode(const webrtc::EncodedImage&, bool, const webrtc::RTPFragmentationHeader*, const webrtc::CodecSpecificInfo*, int64_t)’:
../../third_party/webrtc/modules/video_coding/codecs/vp9/vp9_impl.cc:937:35: error: ‘VPXD_GET_LAST_QUANTIZER’ was not declared in this scope
       vpx_codec_control(decoder_, VPXD_GET_LAST_QUANTIZER, &qp);
                                   ^
../../third_party/webrtc/modules/video_coding/codecs/vp9/vp9_impl.cc:937:7: error: ‘vpx_codec_control_VPXD_GET_LAST_QUANTIZER’ was not declared in this scope
       vpx_codec_control(decoder_, VPXD_GET_LAST_QUANTIZER, &qp);
       ^

See also https://forums.gentoo.org/viewtopic-t-1079520.html

chmod: cannot access '/var/tmp/portage/dev-util/electron-1.6.15/image//usr/lib64/electron-1.6/*.so': No such file or directory

[348/349] x86_64-pc-linux-gnu-g++ -MMD -MF obj/atom/app/electron.atom_main.o.d '-DATOM_PRODUCT_NAME="Electron"' '-DATOM_PROJECT_NAME="electron"' -DENABLE_WEBRTC -DNDEBUG -DV8_USE_EXTERNAL_STARTUP_DATA -DSK_SUPPORT_LEGACY_GETTOPDEVICE -DSK_SUPPORT_LEGACY_BITMAP_CONFIG -DSK_SUPPORT_LEGACY_DEVICE_VIRTUAL_ISOPAQUE -DSK_SUPPORT_LEGACY_N32_NAME -DSK_SUPPORT_LEGACY_SETCONFIG -DSK_IGNORE_ETC1_SUPPORT -DSK_IGNORE_GPU_DITHER -DDISABLE_NACL -DTOOLKIT_VIEWS -DUSE_AURA -DUSE_X11 -DUSE_NSS_CERTS -DUSE_NSS -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -I../.. -I../../vendor/brightray -I../../vendor -I/var/tmp/portage/dev-util/electron-1.6.15/work/electron-1.6.15/chromium -I/var/tmp/portage/dev-util/electron-1.6.15/work/electron-1.6.15/chromium/gpu -I/var/tmp/portage/dev-util/electron-1.6.15/work/electron-1.6.15/chromium/skia/config -I/var/tmp/portage/dev-util/electron-1.6.15/work/electron-1.6.15/chromium/third_party/boringssl/src/include -I/var/tmp/portage/dev-util/electron-1.6.15/work/electron-1.6.15/chromium/third_party/skia/include/core -I/var/tmp/portage/dev-util/electron-1.6.15/work/electron-1.6.15/chromium/third_party/skia/include/config -I/var/tmp/portage/dev-util/electron-1.6.15/work/electron-1.6.15/chromium/third_party/icu/source/common -I/var/tmp/portage/dev-util/electron-1.6.15/work/electron-1.6.15/chromium/third_party/mojo/src -I/var/tmp/portage/dev-util/electron-1.6.15/work/electron-1.6.15/chromium/third_party/khronos -I/var/tmp/portage/dev-util/electron-1.6.15/work/electron-1.6.15/chromium/third_party/WebKit -I/var/tmp/portage/dev-util/electron-1.6.15/work/electron-1.6.15/vendor/brightray/vendor/libchromiumcontent/dist/main/static_library/gen -Wno-inconsistent-missing-override -Wno-undefined-var-template -pthread -Wall -Wextra -Wno-unused-parameter -m64 -fPIC -pthread -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/freetype2 -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/nss -I/usr/include/nspr -Wno-deprecated-register -Wno-sentinel -m64 -march=x86-64 -fdata-sections -ffunction-sections -march=native -O2 -pipe -fno-delete-null-pointer-checks -fno-rtti -fno-exceptions -std=gnu++0x -D__STRICT_ANSI__ -fno-rtti  -c ../../atom/app/atom_main.cc -o obj/atom/app/electron.atom_main.o
[349/349] x86_64-pc-linux-gnu-g++ -Wl,-O1 -pthread -rdynamic -m64 -Wl,--whole-archive /var/tmp/portage/dev-util/electron-1.6.15/work/electron-1.6.15/vendor/brightray/vendor/libchromiumcontent/dist/main/static_library/libwebkitbindings.a /var/tmp/portage/dev-util/electron-1.6.15/work/electron-1.6.15/vendor/brightray/vendor/libchromiumcontent/dist/main/static_library/libnet.a /var/tmp/portage/dev-util/electron-1.6.15/work/electron-1.6.15/vendor/brightray/vendor/libchromiumcontent/dist/main/static_library/libmedia.a /var/tmp/portage/dev-util/electron-1.6.15/work/electron-1.6.15/vendor/brightray/vendor/libchromiumcontent/dist/main/static_library/libservices.a /var/tmp/portage/dev-util/electron-1.6.15/work/electron-1.6.15/vendor/brightray/vendor/libchromiumcontent/dist/main/static_library/libangle.a /var/tmp/portage/dev-util/electron-1.6.15/work/electron-1.6.15/vendor/brightray/vendor/libchromiumcontent/dist/main/static_library/libwebkit.a /var/tmp/portage/dev-util/electron-1.6.15/work/electron-1.6.15/vendor/brightray/vendor/libchromiumcontent/dist/main/static_library/libskia.a /var/tmp/portage/dev-util/electron-1.6.15/work/electron-1.6.15/vendor/brightray/vendor/libchromiumcontent/dist/main/static_library/libbase.a /var/tmp/portage/dev-util/electron-1.6.15/work/electron-1.6.15/vendor/brightray/vendor/libchromiumcontent/dist/main/static_library/libppapi.a /var/tmp/portage/dev-util/electron-1.6.15/work/electron-1.6.15/vendor/brightray/vendor/libchromiumcontent/dist/main/static_library/libwebrtc.a /var/tmp/portage/dev-util/electron-1.6.15/work/electron-1.6.15/vendor/brightray/vendor/libchromiumcontent/dist/main/static_library/libpdfium.a /var/tmp/portage/dev-util/electron-1.6.15/work/electron-1.6.15/vendor/brightray/vendor/libchromiumcontent/dist/main/static_library/libchromiumcontent.a /var/tmp/portage/dev-util/electron-1.6.15/work/electron-1.6.15/vendor/brightray/vendor/libchromiumcontent/dist/main/static_library/libcc.a /var/tmp/portage/dev-util/electron-1.6.15/work/electron-1.6.15/vendor/brightray/vendor/libchromiumcontent/dist/main/static_library/libcomponents.a /var/tmp/portage/dev-util/electron-1.6.15/work/electron-1.6.15/vendor/brightray/vendor/libchromiumcontent/dist/main/static_library/libwebkitmodules.a -Wl,--no-whole-archive -Wl,-rpath=\$ORIGIN/ -rdynamic -Wl,--export-dynamic -pthread -Wl,-rpath=\$ORIGIN/ -rdynamic -m64 -Wl,--gc-sections -Wl,-rpath=\$ORIGIN/lib/ -Wl,-rpath-link=lib/ -o electron -Wl,--start-group obj/atom/app/electron.atom_main.o obj/libelectron_lib.a obj/vendor/brightray/libbrightray.a obj/vendor/breakpad/libbreakpad_client.a -Wl,--end-group lib/libnode.so /var/tmp/portage/dev-util/electron-1.6.15/work/electron-1.6.15/vendor/brightray/vendor/libchromiumcontent/dist/main/shared_library/libv8.so -lpthread -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lfontconfig -lfreetype -ldbus-1 -lX11-xcb -lxcb -lXi -lXcursor -lXdamage -lXrandr -lXcomposite -lXext -lXfixes -lXrender -lX11 -lXtst -lXss -lgmodule-2.0 -lglib-2.0 -lssl3 -lsmime3 -lnss3 -lnssutil3 -lplds4 -lplc4 -lnspr4 -lFLAC -lasound -lavcodec -lavformat -lavutil -lcap -lcrypto -ldl -lexpat -lharfbuzz -ljpeg -lminizip -lpng -lre2 -lresolv -lrt -lsnappy -lssl -lvpx -lwebp -lwebpdemux -lxml2 -lxslt -lz -licui18n -licuuc -licudata
 * PT_PAX marking -m /var/tmp/portage/dev-util/electron-1.6.15/work/electron-1.6.15/out/R/electron with scanelf
 * XATTR_PAX marking -me /var/tmp/portage/dev-util/electron-1.6.15/work/electron-1.6.15/out/R/electron with setfattr
>>> Source compiled.
>>> Test phase [not enabled]: dev-util/electron-1.6.15

>>> Install electron-1.6.15 into /var/tmp/portage/dev-util/electron-1.6.15/image/ category dev-util
chmod: cannot access '/var/tmp/portage/dev-util/electron-1.6.15/image//usr/lib64/electron-1.6/*.so': No such file or directory
 * ERROR: dev-util/electron-1.6.15::atom failed (install phase):
 *   fperms failed
 * 
 * If you need support, post the output of `emerge --info '=dev-util/electron-1.6.15::atom'`,
 * the complete build log and the output of `emerge -pqv '=dev-util/electron-1.6.15::atom'`.
 * The complete build log is located at '/var/tmp/portage/dev-util/electron-1.6.15/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-util/electron-1.6.15/temp/environment'.
 * Working directory: '/var/tmp/portage/dev-util/electron-1.6.15/work/electron-1.6.15'
 * S: '/var/tmp/portage/dev-util/electron-1.6.15/work/electron-1.6.15'

electron-1.4.15 fails to build with cups use flag or jinja>2.8

Just a friendly reminder that these issues still persist if not patched, you might
have a better way of solving this than using bundled ninja/including the cups
header.

Downstream issue at Funtoo: https://bugs.funtoo.org/browse/FL-3545
Basically duplicate of: #14
Which was also tracked here: https://bugs.funtoo.org/browse/FL-3511

I can submit a pull request that uses those patches, however, you might have a
better solution. I'd like to inquire about the direction you're heading with the electron
ebuild, so that I can apply changes properly downstream (that keep things stable):

a) will you create a patch and modified ebuild every time jinja breaks the chromium build?
b) should jinja be slotted?
c) will you use the bundled version of jinja instead? (like Gentoo did in https://bugs.gentoo.org/show_bug.cgi?id=605140)

I have no predilection for any of the solutions. Any one of them could potentially work. I'm only interested in keeping electron stable and changes compatible with Gentoo. It's not my call to decide here.

dev-util/electron sandbox violations

Throughout compilation I guess, mkdir /etc/npm is attempted several times.

Portage stopped after compilation (which succeeded):

>>> Source compiled.
 * --------------------------- ACCESS VIOLATION SUMMARY ---------------------------
 * LOG FILE: "/var/tmp/portage/dev-util/electron-6.1.6-r1/temp/sandbox.log"
 *
VERSION 1.0
FORMAT: F - Function called
FORMAT: S - Access Status
FORMAT: P - Path as passed to function
FORMAT: A - Absolute Path (not canonical)
FORMAT: R - Canonical Path
FORMAT: C - Command Line

F: mkdir
S: deny
P: /etc/npm
A: /etc/npm
R: /etc/npm
C: npm


F: mkdir
S: deny
P: /etc/npm
A: /etc/npm
R: /etc/npm
C: npm

I ran env FEATURES=keepwork emerge -1 --nodeps dev-util/electron and after this and was able to install (without having to rebuild).

This is with USE flags: clang cups proprietary-codecs suid system-ffmpeg system-icu tcmalloc

Contact

Your overlay uses
elprans gmail com
see: https://gpo.zugaina.org/Overlays
as contact, but there is no bugzilla account with this mail address.
There is a bugzilla account elvis magic io which is also connected to the proxy maintained packages.
We need a bugzilla account to assign bugs in your overlay to.

dev-util/electron-6.1.6-r1::atom failed (compile phase) with lto

  • ERROR: dev-util/electron-6.1.6-r1::atom failed (compile phase):
  • ninja -v -j8 -l0 -C out/Release mksnapshot failed

[76/149] python "../../build/toolchain/gcc_link_wrapper.py" --output="./bytecode_builtins_list_generator" -- x86_64-pc-linux-gnu-clang++ -pie -fPIC -Wl,-z,noexecstack -Wl,-z,relro -Wl,-z,now -Wl,-z,defs -Wl,--as-needed -flto=thin -Wl,-plugin-opt,jobs=8 -fwhole-program-vtables -rdynamic -Wl,--no-as-needed -lpthread -Wl,--as-needed -pie -Wl,--disable-new-dtags -Wl,-O1 -Wl,--as-needed -o "./bytecode_builtins_list_generator" -Wl,--start-group @"./bytecode_builtins_list_generator.rsp" -Wl,--end-group -latomic -ldl -lrt
FAILED: bytecode_builtins_list_generator
python "../../build/toolchain/gcc_link_wrapper.py" --output="./bytecode_builtins_list_generator" -- x86_64-pc-linux-gnu-clang++ -pie -fPIC -Wl,-z,noexecstack -Wl,-z,relro -Wl,-z,now -Wl,-z,defs -Wl,--as-needed -flto=thin -Wl,-plugin-opt,jobs=8 -fwhole-program-vtables -rdynamic -Wl,--no-as-needed -lpthread -Wl,--as-needed -pie -Wl,--disable-new-dtags -Wl,-O1 -Wl,--as-needed -o "./bytecode_builtins_list_generator" -Wl,--start-group @"./bytecode_builtins_list_generator.rsp" -Wl,--end-group -latomic -ldl -lrt
/usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: /usr/lib/llvm/8/bin/../lib64/LLVMgold.so: error loading plugin: /usr/lib/llvm/8/bin/../lib64/LLVMgold.so: cannot open shared object file: No such file or directory
clang-8: error: linker command failed with exit code 1 (use -v to see invocation)

As far as I know, thinlto is only supported on lld, but you do not enforce it.

electron-6.1.6-r1.ebuild

	# Disable forced lld, bug 641556
	myconf_gn+=" use_lld=false"


	if use lto; then
		myconf_gn+=" use_thin_lto=true"
	fi

Compare to ungoogled-chromium-79.0.3945.117_p1.ebuild for example

	if use thinlto; then
		# We need to change the default value of import-instr-limit in
		# LLVM to limit the text size increase. The default value is
		# 100, and we change it to 30 to reduce the text size increase
		# from 25% to 10%. The performance number of page_cycler is the
		# same on two of the thinLTO configurations, we got 1% slowdown
		# on speedometer when changing import-instr-limit from 100 to 30.
		append-ldflags "-Wl,-plugin-opt,-import-instr-limit=30"


		append-ldflags "-Wl,--thinlto-jobs=$(makeopts_jobs)"
		myconf_gn+=" use_lld=true"
	fi

You will also need in dependencies:

thinlto? ( >=sys-devel/lld-8.0.0 )

Cannot install vscode: No supported implementation in PYTHON_COMPAT.

It seems Gentoo isn't allowing 2.7 in PYTHON_COMPAT without some special handling. From python-utils-r1.eclass:

        if [[ ! ${supp[@]} ]]; then
                # special-case python2_7 for python-any-r1
                if [[ ${_PYTHON_ALLOW_PY27} ]] && has python2_7 "${PYTHON_COMPAT[@]}"
                then
                        supp+=( python2_7 )
                else
                        die "No supported implementation in PYTHON_COMPAT."
                fi
        fi

If you use python-any-r1.eclass it will allow python2_7 in PYTHON_COMPAT. But maybe it can be hacked in by setting _PYTHON_ALLOW_PY27=1 before the inherit line?

Output from emerge:

Calculating dependencies / * ERROR: app-editors/vscode-1.52.1::electron failed (depend phase):
 *   No supported implementation in PYTHON_COMPAT.
 *
 * Call stack:
 *                 ebuild.sh, line 609:  Called source '/var/db/repos/electron/app-editors/vscode/vscode-1.52.1.ebuild'
 *      vscode-1.52.1.ebuild, line  12:  Called inherit 'multiprocessing' 'python-single-r1' 'rpm' 'xdg-utils'
 *                 ebuild.sh, line 314:  Called __qa_source '/var/db/repos/gentoo/eclass/python-single-r1.eclass'
 - *                 ebuild.sh, line 112:  Called source '/var/db/repos/gentoo/eclass/python-single-r1.eclass'
 *   python-single-r1.eclass, line 269:  Called _python_single_set_globals
 *   python-single-r1.eclass, line 209:  Called _python_set_impls
 *    python-utils-r1.eclass, line 156:  Called die
 * The specific snippet of code:
 *                      die "No supported implementation in PYTHON_COMPAT."
 *
 * If you need support, post the output of `emerge --info '=app-editors/vscode-1.52.1::electron'`,
 * the complete build log and the output of `emerge -pqv '=app-editors/vscode-1.52.1::electron'`.
 * Working directory: '/usr/lib/python3.8/site-packages'
 * S: '/var/tmp/portage/app-editors/vscode-1.52.1/work/vscode-1.52.1'
... done!

!!! All ebuilds that could satisfy "vscode" have been masked.
!!! One of the following masked packages is required to complete your request:
- app-editors/vscode-1.52.1::electron (masked by: corruption)

For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.

Add vscodium editor

Hi! I just noted that you have a recent version of Electron, as well as Atom and VScode editors.

Please, add VSCodium editor too. As well as I noted, the building way may be the same as vscode, but without the Microsoft addons.

Thanks in advice!

Greetings

"invalid code point value" in atom and vscode

Opening php file in atom or vscode gives "invalid code point value" and syntax highlight is broken.
The exact error in vscode is:

[renderer1] [error] invalid code point value: Error: invalid code point value
    at Object.createOnigScanner (/usr/lib64/vscode/node_modules.asar/vscode-textmate/release/main.js:67:24)
    at Grammar.createOnigScanner (/usr/lib64/vscode/node_modules.asar/vscode-textmate/release/main.js:2478:30)
    at RegExpSourceList.compile (/usr/lib64/vscode/node_modules.asar/vscode-textmate/release/main.js:1853:38)
    at BeginEndRule.compile (/usr/lib64/vscode/node_modules.asar/vscode-textmate/release/main.js:2008:45)
    at matchRule (/usr/lib64/vscode/node_modules.asar/vscode-textmate/release/main.js:2724:28)
    at matchRuleOrInjections (/usr/lib64/vscode/node_modules.asar/vscode-textmate/release/main.js:2743:23)
    at scanNext (/usr/lib64/vscode/node_modules.asar/vscode-textmate/release/main.js:2833:17)
    at _tokenizeString (/usr/lib64/vscode/node_modules.asar/vscode-textmate/release/main.js:2826:9)
    at Grammar._tokenize (/usr/lib64/vscode/node_modules.asar/vscode-textmate/release/main.js:2582:25)
    at Grammar.tokenizeLine2 (/usr/lib64/vscode/node_modules.asar/vscode-textmate/release/main.js:2552:22)
    at D.tokenize2 (file:///usr/lib64/vscode/out/vs/workbench/workbench.main.js:4365:788)
    at h._updateTokensUntilLine (file:///usr/lib64/vscode/out/vs/workbench/workbench.main.js:1173:735)
    at h._tokenizeOneLine (file:///usr/lib64/vscode/out/vs/workbench/workbench.main.js:1173:187)
    at P._revalidateTokensNow (file:///usr/lib64/vscode/out/vs/workbench/workbench.main.js:1203:644)
    at P._warmUpTokens (file:///usr/lib64/vscode/out/vs/workbench/workbench.main.js:1203:327)
    at P._tokenizationListener.C.TokenizationRegistry.onDidChange.e (file:///usr/lib64/vscode/out/vs/workbench/workbench.main.js:1177:857)
    at d.fire (file:///usr/lib64/vscode/out/vs/workbench/workbench.main.js:77:983)
    at r.fire (file:///usr/lib64/vscode/out/vs/workbench/workbench.main.js:627:245)
    at register (file:///usr/lib64/vscode/out/vs/workbench/workbench.main.js:627:336)
    at _promises.set.t.then.t (file:///usr/lib64/vscode/out/vs/workbench/workbench.main.js:627:543)

Atom gives a similar error.

Binary distributed vscode works fine.

Could it be, that some of the modules, that are built from source need to be updated?

By the way, do you plan updating atom to the latest version?

=app-editors/atom-1.18.0: Cannot find module '../build/Release/git.node'

Hi,

Atom is compiling fine, but when I run and try to install Atom's packages or check for updates, I get the following errors:

module.js:457
    throw err;
    ^

Error: Cannot find module '../build/Release/git.node'
    at Function.Module._resolveFilename (module.js:455:15)
    at Function.Module._load (module.js:403:25)
    at Module.require (module.js:483:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/usr/lib64/atom/app/apm/node_modules/git-utils/lib/git.js:8:16)
    at Object.<anonymous> (/usr/lib64/atom/app/apm/node_modules/git-utils/lib/git.js:371:4)
    at Module._compile (module.js:556:32)
    at Object.Module._extensions..js (module.js:565:10)
    at Module.load (module.js:473:32)
    at tryModuleLoad (module.js:432:12)

Also, the list of installed packages doesn't show up, it just keep loading ad infinitum. I think it's related to the error above.

dev-util/electron-1.7.15 fails to emerge

Getting this error when trying to emerge electron-1.7.15:

 * Applying electron-1.7.13-v8-crankshaft-rce-fix.patch ...
/var/tmp/portage/dev-util/electron-1.7.15/temp/environment: line 1601: /var/tmp/portage/dev-util/electron-1.7.15/files/electron-1.7.13-v8-crankshaft-rce-fix.patch: No such file or directory                                [ !! ]

Electron-1.3.6 and electron-1.3.13 fail to build with cups USE flag enabled

We've been tracking the issue downstream from gentoo, I've rebuilt both electron-1.3.6 and electron-1.3.13 with and without the cups use flag. The build fails only when the cups use flag is enabled. Cups and cups-filters are both installed on the system as part of a normal gnome install.

Here's the link to our bugtracker:
https://bugs.funtoo.org/browse/FL-3511

Since the ebuild links against your fork of asar I presume you're the author of the ebuild, and I'd very much appreciate any advice on what causes the issue, and if it's a bug reproducible on a gentoo system.

I'd much rather work together on resolving the issue than rewriting the ebuild from scratch. Any pointer on where to start could save me hours of patching and recompiling.

There also might be issues when compiling with jinja >2.8, however, for reference here, jinja is kept at version 2.8.1. Both versions fail to build even with jinja-2.8.1 when the cups use flag is enabled.

Dependency issue with sys-apps/hwids

sys-apps/hwids is marked for removal soon, and has been replaced with sys-apps/hwdata.

!!! All ebuilds that could satisfy "sys-apps/hwids[usb(+)]" have been masked.
!!! One of the following masked packages is required to complete your request:
- sys-apps/hwids-99999999::gentoo (masked by: package.mask, missing keyword)
/var/db/repos/gentoo/profiles/package.mask:
# Mike Gilbert <[email protected]> (2021-12-24)
# Replaced by sys-apps/hwdata. Removal on 2022-01-23.

- sys-apps/hwids-20210613-r2::gentoo (masked by: package.mask)

(dependency required by "dev-util/electron-13.6.2::electron" [ebuild])
(dependency required by "app-editors/vscode-1.63.2-r1::electron" [ebuild])
(dependency required by "app-editors/vscode" [argument])
For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.

Fetching error

I get the error downloading electron-breakpad-e35167de7516448fcc2bf687ad580b9d8b6aedc2.tar.gz:

--2017-09-20 12:48:11--  http://distfiles.gentoo.org/distfiles/electron-breakpad-e35167de7516448fcc2bf687ad580b9d8b6aedc2.tar.gz
Resolving distfiles.gentoo.org... 64.50.236.52, 156.56.247.195, 137.226.34.46, ...
Connecting to distfiles.gentoo.org|64.50.236.52|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2017-09-20 12:48:11 ERROR 404: Not Found.

--2017-09-20 12:48:11--  https://github.com/google/breakpad/archive/e35167de7516448fcc2bf687ad580b9d8b6aedc2.tar.gz
Resolving github.com... 192.30.253.113, 192.30.253.112
Connecting to github.com|192.30.253.113|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://codeload.github.com/google/breakpad/tar.gz/e35167de7516448fcc2bf687ad580b9d8b6aedc2 [following]
--2017-09-20 12:48:12--  https://codeload.github.com/google/breakpad/tar.gz/e35167de7516448fcc2bf687ad580b9d8b6aedc2
Resolving codeload.github.com... 192.30.253.121, 192.30.253.120
Connecting to codeload.github.com|192.30.253.121|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5161275 (4,9M) [application/x-gzip]
Saving to: ‘/usr/portage/distfiles/electron-breakpad-e35167de7516448fcc2bf687ad580b9d8b6aedc2.tar.gz’

     0K .......... .......... .......... .......... ..........  0%  234K 21s
    50K .......... .......... .......... .......... ..........  1%  462K 16s
   100K .......... .......... .......... .......... ..........  2%  496K 14s
   150K .......... .......... .......... .......... ..........  3% 2,42M 11s
   200K .......... .......... .......... .......... ..........  4%  611K 10s
   250K .......... .......... .......... .......... ..........  5% 2,30M 9s
   300K .......... .......... .......... .......... ..........  6% 2,36M 8s
   350K .......... .......... .......... .......... ..........  7% 1,80M 7s
   400K .......... .......... .......... .......... ..........  8% 2,58M 6s
   450K .......... .......... .......... .......... ..........  9% 3,04M 6s
   500K .......... .......... .......... .......... .......... 10% 2,32M 5s
   550K .......... .......... .......... .......... .......... 11% 1,72M 5s
   600K .......... .......... .......... .......... .......... 12% 4,68M 5s
   650K .......... .......... .......... .......... .......... 13% 2,08M 4s
   700K .......... .......... .......... .......... .......... 14% 2,75M 4s
   750K .......... .......... .......... .......... .......... 15% 2,23M 4s
   800K .......... .......... .......... .......... .......... 16% 2,23M 4s
   850K .......... .......... .......... .......... .......... 17% 2,75M 4s
   900K .......... .......... .......... .......... .......... 18% 1,93M 4s
   950K .......... .......... .......... .......... .......... 19% 2,34M 3s
  1000K .......... .......... .......... .......... .......... 20% 2,58M 3s
  1050K .......... .......... .......... .......... .......... 21% 1,95M 3s
  1100K .......... .......... .......... .......... .......... 22%  238K 4s
  1150K .......... .......... .......... .......... .......... 23% 2,32M 4s
  1200K .......... .......... .......... .......... .......... 24% 2,10M 3s
  1250K .......... .......... .......... .......... .......... 25% 4,04M 3s
  1300K .......... .......... .......... .......... .......... 26% 2,45M 3s
  1350K .......... .......... .......... .......... .......... 27% 4,30M 3s
  1400K .......... .......... .......... .......... .......... 28% 47,6M 3s
  1450K .......... .......... .......... .......... .......... 29% 3,82M 3s
  1500K .......... .......... .......... .......... .......... 30% 9,70M 3s
  1550K .......... .......... .......... .......... .......... 31% 3,32M 3s
  1600K .......... .......... .......... .......... .......... 32% 4,45M 3s
  1650K .......... .......... .......... .......... .......... 33% 4,10M 2s
  1700K .......... .......... .......... .......... .......... 34% 4,26M 2s
  1750K .......... .......... .......... .......... .......... 35% 44,4K 4s
  1800K .......... .......... .......... .......... .......... 36% 1,54M 4s
  1850K .......... .......... .......... .......... .......... 37% 1,18M 4s
  1900K .......... .......... .......... .......... .......... 38% 46,6M 4s
  1950K .......... .......... .......... .......... .......... 39% 1,43M 4s
  2000K .......... .......... .......... .......... .......... 40% 52,7M 4s
  2050K .......... .......... .......... .......... .......... 41% 52,4M 3s
  2100K .......... .......... .......... .......... .......... 42% 52,7M 3s
  2150K .......... .......... .......... .......... .......... 43%  101M 3s
  2200K .......... .......... .......... .......... .......... 44% 91,8M 3s
  2250K .......... .......... .......... .......... .......... 45% 1,57M 3s
  2300K .......... .......... .......... .......... .......... 46% 2,38M 3s
  2350K .......... .......... .......... .......... .......... 47% 2,47M 3s
  2400K .......... .......... .......... .......... .......... 48% 2,04M 3s
  2450K .......... .......... .......... .......... .......... 49% 2,94M 3s
  2500K .......... .......... .......... .......... .......... 50% 3,50M 3s
  2550K .......... .......... .......... .......... .......... 51% 2,58M 2s
  2600K .......... .......... .......... .......... .......... 52% 2,57M 2s
  2650K .......... .......... .......... .......... .......... 53% 1,92M 2s
  2700K .......... .......... .......... .......... .......... 54% 2,15M 2s
  2750K .......... .......... .......... .......... .......... 55% 2,47M 2s
  2800K .......... .......... .......... .......... .......... 56% 2,41M 2s
  2850K .......... .......... .......... .......... .......... 57% 1018K 2s
  2900K .......... .......... .......... .......... .......... 58% 1,73M 2s
  2950K .......... .......... .......... .......... .......... 59% 1,65M 2s
  3000K .......... .......... .......... .......... .......... 60% 1,87M 2s
  3050K .......... .......... .......... .......... .......... 61% 2,11M 2s
  3100K .......... .......... .......... .......... .......... 62% 1,83M 2s
  3150K .......... .......... .......... .......... .......... 63% 2,70M 2s
  3200K .......... .......... .......... .......... .......... 64% 2,59M 2s
  3250K .......... .......... .......... .......... .......... 65% 2,49M 2s
  3300K .......... .......... .......... .......... .......... 66% 2,54M 2s
  3350K .......... .......... .......... .......... .......... 67% 2,11M 1s
  3400K .......... .......... .......... .......... .......... 68% 2,02M 1s
  3450K .......... .......... .......... .......... .......... 69% 2,24M 1s
  3500K .......... .......... .......... .......... .......... 70% 2,11M 1s
  3550K .......... .......... .......... .......... .......... 71% 2,46M 1s
  3600K .......... .......... .......... .......... .......... 72% 2,41M 1s
  3650K .......... .......... .......... .......... .......... 73% 2,23M 1s
  3700K .......... .......... .......... .......... .......... 74% 2,67M 1s
  3750K .......... .......... .......... .......... .......... 75% 2,77M 1s
  3800K .......... .......... .......... .......... .......... 76% 2,43M 1s
  3850K .......... .......... .......... .......... .......... 77% 2,55M 1s
  3900K .......... .......... .......... .......... .......... 78% 1,96M 1s
  3950K .......... .......... .......... .......... .......... 79% 2,70M 1s
  4000K .......... .......... .......... .......... .......... 80% 3,79M 1s
  4050K .......... .......... .......... .......... .......... 81% 2,45M 1s
  4100K .......... .......... .......... .......... .......... 82% 2,70M 1s
  4150K .......... .......... .......... .......... .......... 83% 3,06M 1s
  4200K .......... .......... .......... .......... .......... 84% 2,12M 1s
  4250K .......... .......... .......... .......... .......... 85% 2,44M 1s
  4300K .......... .......... .......... .......... .......... 86% 2,63M 1s
  4350K .......... .......... .......... .......... .......... 87% 2,72M 0s
  4400K .......... .......... .......... .......... .......... 88% 3,63M 0s
  4450K .......... .......... .......... .......... .......... 89% 2,57M 0s
  4500K .......... .......... .......... .......... .......... 90% 3,05M 0s
  4550K .......... .......... .......... .......... .......... 91% 1,63M 0s
  4600K .......... .......... .......... .......... .......... 92% 2,06M 0s
  4650K .......... .......... .......... .......... .......... 93% 5,31M 0s
  4700K .......... .......... .......... .......... .......... 94%  674K 0s
  4750K .......... .......... .......... .......... .......... 95% 2,46M 0s
  4800K .......... .......... .......... .......... .......... 96% 4,04M 0s
  4850K .......... .......... .......... .......... .......... 97% 2,89M 0s
  4900K .......... .......... .......... .......... .......... 98% 2,86M 0s
  4950K .......... .......... .......... .......... .......... 99% 2,90M 0s
  5000K .......... .......... .......... ..........           100% 1,87M=3,7s

2017-09-20 12:48:16 (1,33 MB/s) - ‘/usr/portage/distfiles/electron-breakpad-e35167de7516448fcc2bf687ad580b9d8b6aedc2.tar.gz’ saved [5161275/5161275]

!!! Fetched file: electron-breakpad-e35167de7516448fcc2bf687ad580b9d8b6aedc2.tar.gz VERIFY FAILED!
!!! Reason: Filesize does not match recorded size
!!! Got:      5161275
!!! Expected: 5161167
Refetching... File renamed to '/usr/portage/distfiles/electron-breakpad-e35167de7516448fcc2bf687ad580b9d8b6aedc2.tar.gz._checksum_failure_.hxgldpks'

!!! Couldn't download 'electron-breakpad-e35167de7516448fcc2bf687ad580b9d8b6aedc2.tar.gz'. Aborting.
 * Fetch failed for 'dev-util/electron-1.6.11', Log file:
 *  '/var/tmp/portage/dev-util/electron-1.6.11/temp/build.log'

vscode nodejs dependency issue

vscode depends on nodejs like this:

  >=net-libs/nodejs-6.11.0[${PYTHON_USEDEP}]

It worked fine until they replaced python-single-r1 with python-any-r1 in mainline nodejs ebuild.

electron dependency looks like this:

 >=net-libs/nodejs-6.9.4

Please, remove [${PYTHON_USEDEP}] from vscode ebuild. I could do a PR if you'd like.

electron-1.4.12 is out :)

I just tried building it by simply adjusting the version number for the ebuild and the patches. The official build ships with Node 6.5.0 and they are now using browserify during the build process, so I simply installed the latter through npm to some directory I have in my $PATH, but kept Node 6.3.0, as specified via the commit hash in the ebuild. I'll see what happens once compilation is done and try it with Node 6.5.0 as well. Would it make sense to add npm as a build dependency and add npm install and adjust the $PATH during the (e)merge?

Anyway, it's an awesome job you've done here! I've seen the TODOs in the ebuild, maybe I'll give them a shot :)

dev-util/electron/electron-6.1.6 needs icu-65.patch

Which fixes missing comma:

diff --git a/third_party/blink/renderer/core/dom/document.cc b/third_party/blink/renderer/core/dom/document.cc
index 5a62770..1fae2aa 100644
--- a/third_party/blink/renderer/core/dom/document.cc
+++ b/third_party/blink/renderer/core/dom/document.cc
@@ -6192,7 +6192,7 @@ static ParseQualifiedNameResult ParseQualifiedNameInternal(
 
   for (unsigned i = 0; i < length;) {
     UChar32 c;
-    U16_NEXT(characters, i, length, c)
+    U16_NEXT(characters, i, length, c);
     if (c == ':') {
       if (saw_colon)
         return ParseQualifiedNameResult(kQNMultipleColons);

dev-util/electron-6.1.6-r1::atom failed (compile phase) with lto (seccomp issue)

Manually adding myconf_gn+=" use_lld=true" still results in a compilation failure

  • ERROR: dev-util/electron-6.1.6-r1::atom failed (compile phase):
  • ninja -v -j8 -l0 -C out/Release electron chromedriver failed
[2458/16559] x86_64-pc-linux-gnu-clang++ -MMD -MF obj/sandbox/linux/seccomp_bpf/bpf_dsl.o.d -DSANDBOX_IMPLEMENTATION -DUSE_UDEV -DUSE_AURA=1 -DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1 -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DCHROMIUM_BUILD -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_32 -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_26 -I../.. -Igen -I../../third_party/boringssl/src/include -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector -funwind-tables -fPIC -pthread -fcolor-diagnostics -fmerge-all-constants -flto=thin -fsplit-lto-unit -fwhole-program-vtables -Wno-builtin-macro-redefined -D__DATE__= -D__TIME__= -D__TIMESTAMP__= -no-canonical-prefixes -Wimplicit-fallthrough -Wthread-safety -Wextra-semi -Wno-missing-field-initializers -Wno-unused-parameter -Wno-c++11-narrowing -Wno-unneeded-internal-declaration -Wno-undefined-var-template -Wno-ignored-pragma-optimize -fno-omit-frame-pointer -fvisibility=hidden -Wheader-hygiene -Wstring-conversion -Wtautological-overlap-compare -fno-lto -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/lib64/libffi-3.3_rc0/include -std=c++14 -fno-exceptions -fno-rtti -fvisibility-inlines-hidden -march=haswell -O2 -pipe -c ../../sandbox/linux/bpf_dsl/bpf_dsl.cc -o obj/sandbox/linux/seccomp_bpf/bpf_dsl.o
FAILED: obj/sandbox/linux/seccomp_bpf/bpf_dsl.o 
x86_64-pc-linux-gnu-clang++ -MMD -MF obj/sandbox/linux/seccomp_bpf/bpf_dsl.o.d -DSANDBOX_IMPLEMENTATION -DUSE_UDEV -DUSE_AURA=1 -DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1 -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DCHROMIUM_BUILD -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_32 -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_26 -I../.. -Igen -I../../third_party/boringssl/src/include -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector -funwind-tables -fPIC -pthread -fcolor-diagnostics -fmerge-all-constants -flto=thin -fsplit-lto-unit -fwhole-program-vtables -Wno-builtin-macro-redefined -D__DATE__= -D__TIME__= -D__TIMESTAMP__= -no-canonical-prefixes -Wimplicit-fallthrough -Wthread-safety -Wextra-semi -Wno-missing-field-initializers -Wno-unused-parameter -Wno-c++11-narrowing -Wno-unneeded-internal-declaration -Wno-undefined-var-template -Wno-ignored-pragma-optimize -fno-omit-frame-pointer -fvisibility=hidden -Wheader-hygiene -Wstring-conversion -Wtautological-overlap-compare -fno-lto -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/lib64/libffi-3.3_rc0/include -std=c++14 -fno-exceptions -fno-rtti -fvisibility-inlines-hidden -march=haswell -O2 -pipe -c ../../sandbox/linux/bpf_dsl/bpf_dsl.cc -o obj/sandbox/linux/seccomp_bpf/bpf_dsl.o
x86_64-pc-linux-gnu-clang++: error: invalid argument '-fwhole-program-vtables' only allowed with '-flto'
[2459/16559] x86_64-pc-linux-gnu-clang++ -MMD -MF obj/sandbox/linux/seccomp_bpf/codegen.o.d -DSANDBOX_IMPLEMENTATION -DUSE_UDEV -DUSE_AURA=1 -DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1 -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DCHROMIUM_BUILD -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_32 -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_26 -I../.. -Igen -I../../third_party/boringssl/src/include -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector -funwind-tables -fPIC -pthread -fcolor-diagnostics -fmerge-all-constants -flto=thin -fsplit-lto-unit -fwhole-program-vtables -Wno-builtin-macro-redefined -D__DATE__= -D__TIME__= -D__TIMESTAMP__= -no-canonical-prefixes -Wimplicit-fallthrough -Wthread-safety -Wextra-semi -Wno-missing-field-initializers -Wno-unused-parameter -Wno-c++11-narrowing -Wno-unneeded-internal-declaration -Wno-undefined-var-template -Wno-ignored-pragma-optimize -fno-omit-frame-pointer -fvisibility=hidden -Wheader-hygiene -Wstring-conversion -Wtautological-overlap-compare -fno-lto -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/lib64/libffi-3.3_rc0/include -std=c++14 -fno-exceptions -fno-rtti -fvisibility-inlines-hidden -march=haswell -O2 -pipe -c ../../sandbox/linux/bpf_dsl/codegen.cc -o obj/sandbox/linux/seccomp_bpf/codegen.o
FAILED: obj/sandbox/linux/seccomp_bpf/codegen.o 
x86_64-pc-linux-gnu-clang++ -MMD -MF obj/sandbox/linux/seccomp_bpf/codegen.o.d -DSANDBOX_IMPLEMENTATION -DUSE_UDEV -DUSE_AURA=1 -DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1 -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DCHROMIUM_BUILD -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_32 -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_26 -I../.. -Igen -I../../third_party/boringssl/src/include -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector -funwind-tables -fPIC -pthread -fcolor-diagnostics -fmerge-all-constants -flto=thin -fsplit-lto-unit -fwhole-program-vtables -Wno-builtin-macro-redefined -D__DATE__= -D__TIME__= -D__TIMESTAMP__= -no-canonical-prefixes -Wimplicit-fallthrough -Wthread-safety -Wextra-semi -Wno-missing-field-initializers -Wno-unused-parameter -Wno-c++11-narrowing -Wno-unneeded-internal-declaration -Wno-undefined-var-template -Wno-ignored-pragma-optimize -fno-omit-frame-pointer -fvisibility=hidden -Wheader-hygiene -Wstring-conversion -Wtautological-overlap-compare -fno-lto -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/lib64/libffi-3.3_rc0/include -std=c++14 -fno-exceptions -fno-rtti -fvisibility-inlines-hidden -march=haswell -O2 -pipe -c ../../sandbox/linux/bpf_dsl/codegen.cc -o obj/sandbox/linux/seccomp_bpf/codegen.o
x86_64-pc-linux-gnu-clang++: error: invalid argument '-fwhole-program-vtables' only allowed with '-flto'

Electron 2.0.17 is not compatible with media-libs/libvpx-1.8.x

Just noticed this today, I had keyworded >= 1.7.0 libvpx for electron and after it updated to 1.8.0 electron could no longer be built.

Because this issue traces back to the embedded chromium source code, and the issue has been fixed in Chromium, it'll probably be resolved in the next release that significantly updates the embedded chromium.

If interested i can send a PR to lock 2.0.17 to 1.7.0, otherwise this issue is mainly intended to track further developments on this.

dev-util/electron-1.7.6: won't build with 'gtk3' USE flag enabled

Hi,

As the title said, it seems that use_gtk3=true disables libgtk2ui, which is a dependency for... chromium itself(?). I got the following error:

Building gn using itself to out/Release...
DEBUG:root:Running: /var/tmp/notmpfs/portage/dev-util/electron-1.7.6/work/temp/tmpmSa7NO/gn gen /var/tmp/notmpfs/portage/dev-util/electron-1.7.6/work/electron-1.7.6/chromium/out/Release --args= is_debug=false enable_nacl=false use_cups=false use_gconf=false use_gnome_keyring=false use_gtk3=true use_kerberos=false use_pulseaudio=true fieldtrial_testing_like_official_build=true is_clang=false use_gold=false use_sysroot=false linux_use_bundled_binutils=false proprietary_codecs=true ffmpeg_branding="Chrome" google_api_key="AIzaSyDEAOvatFo0eTgsV_ZlEzx0ObmepsMzfAc" google_default_client_id="329227923882.apps.googleusercontent.com" google_default_client_secret="vgKG0NNv7GoDpbtoFNLxCUXu" treat_warnings_as_errors=false fatal_linker_warnings=false custom_toolchain="/var/tmp/notmpfs/portage/dev-util/electron-1.7.6/files/toolchain:default" root_extra_deps = ["//chromiumcontent:chromiumcontent"] is_electron_build = true is_component_build = false use_allocator="none" is_debug=false
ERROR Unresolved dependencies.
//chromiumcontent:targets(/var/tmp/notmpfs/portage/dev-util/electron-1.7.6/files/toolchain:default)
  needs //chrome/browser/ui/libgtkui:libgtk2ui(/var/tmp/notmpfs/portage/dev-util/electron-1.7.6/files/toolchain:default)

New version of electron in atom

is there a way to build atom with fresh (1.3.5) version of electron? If not current version, can you add the ebuild for the latest beta version?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.