/usr/lib/chromium/chromium: error while loading shared libraries: libre2.so.7: cannot open shared object file: No such file or directory
I believe this is related to the comment from the @ffmorgner
Git Clone URL: | https://aur.archlinux.org/ungoogled-chromium.git (read-only, click to copy) |
---|---|
Package Base: | ungoogled-chromium |
Description: | A lightweight approach to removing Google web service dependency |
Upstream URL: | https://github.com/ungoogled-software/ungoogled-chromium |
Keywords: | blink browser privacy web |
Licenses: | BSD-3-Clause |
Conflicts: | chromedriver, chromium |
Provides: | chromedriver, chromium |
Submitter: | ilikenwf |
Maintainer: | JstKddng (networkException) |
Last Packager: | networkException |
Votes: | 353 |
Popularity: | 3.68 |
First Submitted: | 2016-12-19 08:08 (UTC) |
Last Updated: | 2025-01-09 17:44 (UTC) |
« First ‹ Previous 1 .. 30 31 32 33 34 35 36 37 38 39 40 .. 66 Next › Last »
/usr/lib/chromium/chromium: error while loading shared libraries: libre2.so.7: cannot open shared object file: No such file or directory
I believe this is related to the comment from the @ffmorgner
Since the last bump on 2020-07-01, re2 has been updated in [extra] (on 2020-07-07), requiring a rebuild of this package. Could you please bump the pkgrel in order to facilitate the rebuild on the user side?
I get a linking error with the latest update (.116). I ran LD with -v, and this is the output:
[7677/7677] LINK ./chrome
FAILED: chrome
clang++ -Wl,--version-script=../../build/linux/chrome.map -Wl,--fatal-warnings -Wl,--build-id=sha1 -fPIC -Wl,-z,noexecstack -Wl,-z,relro -Wl,-z,now -Wl,-z,defs -Wl,--as-needed -fuse-ld=lld -Wl,--icf=all -Wl,--color-diagnostics -flto=thin -Wl,--thinlto-jobs=8 -Wl,--thinlto-cache-dir=thinlto-cache -Wl,--thinlto-cache-policy,cache_size=10\%:cache_size_bytes=10g:cache_size_files=100000 -Wl,--lto-O0 -fwhole-program-vtables -m64 -Wl,-O2 -Wl,--gc-sections -rdynamic -fsanitize=cfi-vcall -fsanitize=cfi-icall -pie -Wl,--disable-new-dtags -Wl,-O3,--sort-common,--as-needed,-z,relro,-z,now,-v -o "./chrome" -Wl,--start-group @"./chrome.rsp" -Wl,--end-group -latomic -ldl -lpthread -lrt -lX11 -lX11-xcb -lxcb -lxcb-dri3 -lXcomposite -lXcursor -lXdamage -lXext -lXfixes -lXi -lXrender -lXtst -lgmodule-2.0 -lglib-2.0 -lgobject-2.0 -lgthread-2.0 -licui18n -licuuc -licudata -lsmime3 -lnss3 -lnssutil3 -lplds4 -lplc4 -lnspr4 -latk-1.0 -latk-bridge-2.0 -lcups -lfontconfig -ldbus-1 -lz -lresolv -lgio-2.0 -lwebpdemux -lwebpmux -lwebp -lfreetype -ljpeg -lexpat -lharfbuzz-subset -lharfbuzz -ldrm -lm -lopus -lavcodec -lavformat -lavutil -lvpx -lXrandr -lre2 -lpci -lgbm -lXss -lasound -lpulse -lsnappy -lpangocairo-1.0 -lpango-1.0 -lcairo -lva -lxml2 -latspi -lFLAC -lminizip -lgtk-3 -lgdk-3 -lcairo-gobject -lgdk_pixbuf-2.0 -lxslt
LLD 10.0.0 (compatible with GNU linkers)
clang-10: error: unable to execute command: Terminated
clang-10: error: linker command failed due to signal (use -v to see invocation)
ninja: build stopped: subcommand failed.
==> ERROR: A failure occurred in build().
Aborting...
error making: %!s(func() string=0x55a8623fce80)
Update: Has nothing to do with package. I had setup LTO wrong, and that caused a link error. For anybody that also has the same problem, take a look at your LTO options or just disable it.
@Jojii
well, the makepkg logs would be nice to have.
I also triggered a rebuild on the OBS just in case and it was succesful. https://build.opensuse.org/package/live_build_log/home:justkidding:arch/ungoogled-chromium/standard/x86_64
@JstKddng I have no idea where I should look for helpful logs. I don't remove those containers but I don't get much information from them too.
@jojii
I'm gonna need some logs before I can help. Are you immediately deleting the docker container after building?
@JstKddng nope I can't find any log where I could get more informations from
@followait
Depends on how much cores/threads you have. I'd recommend to have swap, at least a swapfile during compilation.
@Jojii
Do you have an error message?
My VM where I compile this inside a docker container shuts down/crashes after some time compiling this package :(
@JstKddng without swap, 16G memory not enough?
Pinned Comments
JstKddng commented on 2022-05-06 14:37 (UTC) (edited on 2022-06-27 13:48 (UTC) by JstKddng)
A new va-api patch for wayland has been added. Required flags for it to work are the following, thanks to @acidunit
JstKddng commented on 2020-07-19 06:34 (UTC)
You can get prebuilt binaries here:
https://github.com/ungoogled-software/ungoogled-chromium-archlinux#binary-downloads
seppia commented on 2018-12-12 21:34 (UTC)
Please do NOT flag this package as out of date in relation to official chromium releases.
This is NOT Google Chromium and new releases come after additional work of the ungoogled-chromium contributors, so they may not be ready, nor available for days or even weeks after a new version of official chromium is released.
Please refer to https://github.com/Eloston/ungoogled-chromium/tags for ungoogled-chromium releases. Use those and please flag this package as out of date only if a newer release is present there. I will update the PKGBUILD as soon as I can every time a new release comes out.
Thanks