content_shell can't find libgcrypt.so.11
Reported by
jwo...@igalia.com,
Jun 15 2016
|
|||||||||||
Issue descriptionWhen running: python third_party/WebKit/Tools/Scripts/run-webkit-tests -t Release I get this error: /home/josh/chromium/src/out/Release/content_shell: error while loading shared libraries: libgcrypt.so.11: cannot open shared object file: No such file or directory I am on Ubuntu 15.10 wily, which has libgcrypt.so.20, not libgcrypt.so.11.
,
Jun 15 2016
Try building without the sysroot. GYP: use_sysroot=0, GN: use_sysroot=false.
,
Jun 15 2016
,
Jul 13 2016
,
Jul 13 2016
,
Aug 23 2016
@jwolfe: Could you please provide an update on this issue as per #5.
,
Aug 23 2016
The suggestion in Comment 2 works around the problem. Is there anything else I can do to help?
,
Aug 23 2016
You will need to do one of 1. Change your sysroot to use libgcrypt.so.20. The jessie sysroot probably has the updated libgcrypt, but you'll probably run into other problems 2. Add libgcrypt.so.11 to your system I'd recommend #2 You can download the appropriate package for your arch here http://packages.ubuntu.com/trusty/libgcrypt11 Do not install the package on your system. Only extract /lib/x86_64-linux-gnu/libgcrypt.so.11 manually
,
Aug 23 2016
(Forgot to mention that now I'm on Ubuntu 16.04 xenial, but everything relevant to this issue seems the same anyway. And I will likely update to Ubuntu 16.10 yakkety when it becomes available.) Is my development environment "supported" by this project? I.e. is everything supposed to work out of the box, or am I expected to work around problems like this? It sounds like Comment 8 is proposing a work around for the problem, but the work around in Comment 2 seems to work already. I originally opened this issue because this project did not work out of the box for my environment. Is that even a goal for this project? Perhaps the setup instructions could be updated?
,
Aug 26 2016
,
Sep 2 2016
Thank you for providing more feedback. Adding requester "thestig@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 2 2016
We certainly want to support the latest Ubuntu LTS release as a developer platform. It's just that we still have bots running on Ubuntu 12.04 and it's taken longer than expected to get rid of them.
,
Sep 13 2016
,
Sep 13 2016
It appears that gcrypt isn't really needed by the build, but it is getting pulled in via the pkg-config in the sysroot and not stripped by the linker for reasons I don't yet understand. And, yes, things should work "out of the box", and it's a bug that they don't.
,
Sep 13 2016
Looks like we're only passing -Wl,--as-needed to the linker in optimized builds (hence, only release). We should probably be passing it always, since there doesn't appear to be a good reason not to.
,
Sep 14 2016
,
Sep 15 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/ea511c32453aadb84ae6d8cb0daaad43c00092d0 commit ea511c32453aadb84ae6d8cb0daaad43c00092d0 Author: thomasanderson <thomasanderson@google.com> Date: Thu Sep 15 01:17:20 2016 Link with -Wl,--as-needed on non-optimized builds BUG= 620169 R=dpranke@chromium.org Review-Url: https://codereview.chromium.org/2338373003 Cr-Commit-Position: refs/heads/master@{#418743} [modify] https://crrev.com/ea511c32453aadb84ae6d8cb0daaad43c00092d0/build/config/compiler/BUILD.gn
,
Sep 15 2016
|
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by scottmg@chromium.org
, Jun 15 2016