network-manager-applet uses differrent naming scheme from the VPN plug-ins.
Let’s revert to the previous state, for now, to fix eval. We can do the rename later.
This reverts commit cecb014d5d.
Follow-up to #170730
After release, the v8.0.7 tag had been re-tagged to a newer but broken state.
This commit does not change the built program but only ensures that it continues
to be buildable.
A lot of bloat had been accumulated through updates (e.g. with linphone
migrating from Gtk to Qt, or linphone being split to liblinphone &
linphone-desktop).
Method: Through trial and error. Delete all dependencies, try to build, try to
run, reintroduce missing dependencies.
I have tested everything I could, but it is possible that some optional
features have been silently disabled with dependencies not being found now.
(Codecs, encryption schemes, etc...)
LLVM 14 doesn't support those build flags yet
(-no-opaque-pointers is the argument for -Xclang):
error: unknown argument: '-no-opaque-pointers'
Those build flags were added in the following commit:
003067c130
This fixes the following error:
configuring
ERROR at //infra/orchestrator/BUILD.gn:38:17: Could not read file.
pydeps_file = "//third_party/blink/tools/merge_web_test_results.pydeps"
^--------------------------------------------------------
I resolved this to "/build/chromium-102.0.5005.27/third_party/blink/tools/merge_web_test_results.pydeps".
See //infra/orchestrator/BUILD.gn:37:1: whence it was called.
python_library("blink_merge_web_test_results_py") {
^--------------------------------------------------
See //BUILD.gn:89:5: which caused the file to be included.
"//infra/orchestrator:orchestrator_all",
^--------------------------------------
It's a known upstream issue when building from the generated tarballs:
- https://bugs.chromium.org/p/chromium/issues/detail?id=1313361
- https://chromium-review.googlesource.com/c/chromium/src/+/3457503