Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 655990 - www-client/chromium - /usr/lib64/chromium-browser/chrome contains writable and executable sections
Summary: www-client/chromium - /usr/lib64/chromium-browser/chrome contains writable an...
Status: CONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Chromium Project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-17 21:59 UTC by Povilas Brilius
Modified: 2018-08-13 11:14 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
add sys-devel/lld as dependency, correct some flags/comments (chromium-67.0.3396.62.ebuild.patch,935 bytes, patch)
2018-06-05 15:33 UTC, Ian Moone
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Povilas Brilius 2018-05-17 21:59:43 UTC
usr/lib64/chromium-browser/chrome contain writable and executable sections. Files with such sections will not work properly (or at all!) on some architectures/operating systems.
Comment 1 Agostino Sarubbo gentoo-dev 2018-05-18 13:37:03 UTC
can you attach the full build log?
Comment 2 Povilas Brilius 2018-05-18 14:20:16 UTC
The portage elog was configured to echo only, reconfigured to also save, plus, elog classes didn't include qa, that's why it was only saved during building, but not retained afterwards.
Comment 3 Mike Gilbert gentoo-dev 2018-05-29 03:26:13 UTC
From the out/Release directory:

> --- --- RWX  ./chrome
> !WX --- ---  ./obj/third_party/crashpad/crashpad/util/util/capture_context_linux.o
> !WX --- ---  ./obj/third_party/crashpad/crashpad/client/client/crashpad_info_note.o
> !WX --- ---  ./obj/third_party/boringssl/boringssl_asm/x86_64-mont5.o
> !WX --- ---  ./obj/third_party/boringssl/boringssl_asm/x86_64-mont.o
> !WX --- ---  ./obj/third_party/boringssl/boringssl_asm/sha512-x86_64.o
> !WX --- ---  ./obj/third_party/boringssl/boringssl_asm/vpaes-x86_64.o
> !WX --- ---  ./obj/third_party/boringssl/boringssl_asm/sha256-x86_64.o
> !WX --- ---  ./obj/third_party/boringssl/boringssl_asm/sha1-x86_64.o
> !WX --- ---  ./obj/third_party/boringssl/boringssl_asm/rsaz-avx2.o
> !WX --- ---  ./obj/third_party/boringssl/boringssl_asm/rdrand-x86_64.o
> !WX --- ---  ./obj/third_party/boringssl/boringssl_asm/p256-x86_64-asm.o
> !WX --- ---  ./obj/third_party/boringssl/boringssl_asm/md5-x86_64.o
> !WX --- ---  ./obj/third_party/boringssl/boringssl_asm/ghash-x86_64.o
> !WX --- ---  ./obj/third_party/boringssl/boringssl_asm/bsaes-x86_64.o
> !WX --- ---  ./obj/third_party/boringssl/boringssl_asm/aes-x86_64.o
> !WX --- ---  ./obj/third_party/boringssl/boringssl_asm/aesni-x86_64.o
> !WX --- ---  ./obj/third_party/boringssl/boringssl_asm/aesni-gcm-x86_64.o
> !WX --- ---  ./obj/third_party/boringssl/boringssl_asm/chacha20_poly1305_x86_64.o
> !WX --- ---  ./obj/third_party/boringssl/boringssl_asm/aes128gcmsiv-x86_64.o
> !WX --- ---  ./obj/third_party/boringssl/boringssl_asm/chacha-x86_64.o
> !WX --- ---  ./obj/third_party/blink/renderer/platform/heap/asm/asm/SaveRegisters_x86.o
Comment 4 Ian Moone 2018-06-05 15:23:29 UTC
I was experimenting with some flags, and accidental discovered that adding sys-devel/lld as a new dependency and with these flags (is_cfi=true, use_gold=true and use_lld=true) fixed the issue for me. Probably the last 2 flags are already enabled by default?!

It seems to resolves #641556 too. But I'm not so sure, as I've only tested 67.0.3396.62 with clang-6.
Comment 5 Ian Moone 2018-06-05 15:33:31 UTC
Created attachment 534902 [details, diff]
add sys-devel/lld as dependency, correct some flags/comments
Comment 6 Mike Gilbert gentoo-dev 2018-06-05 16:43:32 UTC
Using lld probably just masks the problem here.