1 |
FYI this info and use flags worked for me to get a clean *electron* build |
2 |
(with also getting eg *nodejs *dependency). I think also works for |
3 |
chromium. I doubt "static-libs" is making any difference: |
4 |
|
5 |
*/etc/portage>* emerge --info electron |
6 |
|
7 |
dev-libs/openssl-1.0.2l::gentoo was built with the following: |
8 |
USE="asm sslv2 sslv3 static-libs tls-heartbeat zlib -bindist -gmp -kerberos |
9 |
-rfc3779 -sctp -test -vanilla" |
10 |
|
11 |
*/etc/portage>* emerge --info electron |
12 |
|
13 |
dev-libs/openssl-1.0.2l::gentoo was built with the following: |
14 |
USE="asm sslv2 sslv3 static-libs tls-heartbeat zlib -bindist -gmp -kerberos |
15 |
-rfc3779 -sctp -test -vanilla" |
16 |
|
17 |
*/etc/portage>* egrep -r "(ssl|electron|nodejs)" pack* |
18 |
|
19 |
package.accept_keywords:>=dev-libs/openssl-1.0.2l ~amd64 |
20 |
package.accept_keywords:=dev-util/electron-1.3.13-r1 ~amd64 |
21 |
|
22 |
package.mask/mask:=dev-libs/openssl-1.0.1 |
23 |
package.mask/mask:=dev-libs/openssl-1.0.2g |
24 |
package.mask/mask:=dev-libs/openssl-1.1.0f |
25 |
package.use/use:>=dev-libs/openssl-1.0.2l ssl sslv2 sslv3 static-libs |
26 |
|
27 |
|
28 |
On Mon, Sep 4, 2017 at 4:23 PM, Damo Brisbane <dhatchett2@×××××.com> wrote: |
29 |
|
30 |
> Emerge -pv openssl: |
31 |
> |
32 |
> [ebuild R ] dev-libs/openssl-1.0.2l::gentoo USE="asm sslv3 |
33 |
> tls-heartbeat zlib -bindist -gmp -kerberos -rfc3779 -sctp -sslv2 |
34 |
> -static-libs {-test} -vanilla"... |
35 |
> |
36 |
> I figured ssl better off without it; I think the issue with this package |
37 |
> is it builds it's own version of chromium as part of the emerge, and I |
38 |
> think this is where the ssl dependency comes in. Right though, I think |
39 |
> package maintainer is where I need to head to next. |
40 |
> |
41 |
> Thanks |
42 |
> |
43 |
> On Sat, Sep 2, 2017 at 11:40 AM, Adam Carter <adamcarter3@×××××.com> |
44 |
> wrote: |
45 |
> |
46 |
>> On Sat, Sep 2, 2017 at 6:26 AM, Damo Brisbane <dhatchett2@×××××.com> |
47 |
>> wrote: |
48 |
>> |
49 |
>>> Hello, |
50 |
>>> |
51 |
>>> I am having troubles installing dev-util/electron, related to linking in |
52 |
>>> "ssl3" in the final step of the ebuild, from build log: |
53 |
>>> |
54 |
>>> /usr/lib/gcc/x86_64-pc-linux-gnu/6.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: |
55 |
>>> cannot find -lssl3 |
56 |
>>> |
57 |
>>> |
58 |
>>> FYI on ssl, I only want a "working/current" ssl and/or tls installation |
59 |
>>> and I don't care for the details around the installation other than I would |
60 |
>>> like - as much as possible - "ssl" to be future proof and compatible with |
61 |
>>> current and new installs; in this case I just want electron, and I can't |
62 |
>>> install the package because of this linking error. I can successfully build |
63 |
>>> by hacking the final link step and simply remove the reference to "-lssl", |
64 |
>>> below: |
65 |
>>> |
66 |
>>> |
67 |
>>> > cd $PORTAGE_TMPDIR/dev-util/electron-1.3.13-r1/work/chromium-52 |
68 |
>>> .0.2743.82/out/R |
69 |
>>> > x86_64-pc-linux-gnu-g++ -Wl,-O1 -Wl,--a ....obj/atom/app/electron.atom_main.o obj/libelectron_lib.a |
70 |
>>> o... lib/libnode.so lib/libv8.so -lz -lhttp_parser -lssl -lcrypto - |
71 |
>>> |
72 |
>>> |
73 |
>>> and compiles fine. |
74 |
>>> |
75 |
>>> There are no "ssl" use flags on electron?: |
76 |
>>> |
77 |
>> |
78 |
>> My first guess would be that your openssl is not compiled with sslv3. The |
79 |
>> ebuild for electron only asks for >=dev-libs/openssl-1.0.2g:0=[-bindist] |
80 |
>> not openssl[sslv3]. If that's the problem then there's a bug in electrons |
81 |
>> ebuild. |
82 |
>> |
83 |
>> What does emerge -pv openssl show for use flags? |
84 |
>> |
85 |
>> However, ssl is pretty much deprecated these days due to security issues, |
86 |
>> so unless you have a need to support something that cant do TLS, you're |
87 |
>> better off leaving it out. Another issue may be that -lssl may be a loose |
88 |
>> term for SSL+TLS... |
89 |
>> |
90 |
> |
91 |
> |