Bug 278464 - www/ungoogled-chromium: 119.0.6045.199 fails to start: ld-elf.so.1: /usr/local/share/ungoogled-chromium/ungoogled-chromium: Undefined symbol "_ZN6snappy11RawCompressEPKcmPcPm"
Summary: www/ungoogled-chromium: 119.0.6045.199 fails to start: ld-elf.so.1: /usr/loca...
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-19 15:33 UTC by Dave Cottlehuber
Modified: 2024-05-05 15:59 UTC (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dave Cottlehuber freebsd_committer freebsd_triage 2024-04-19 15:33:32 UTC 
After recent archivers/snappy bump to 1.2.0[1], this port fails to start.

ld-elf.so.1: /usr/local/share/ungoogled-chromium/ungoogled-chromium: Undefined symbol "_ZN6snappy11RawCompressEPKcmPcPm"

[1]: https://cgit.freebsd.org/ports/commit/?id=fa01e117e24fed6cf7b52d90a8d82b4bee06fe21

similar downstream issues elsewhere outside FreeBSD https://github.com/conda-forge/snappy-feedstock/issues/35

Also, port at 119.0.6045.199 is a long way behind upstream ungoogled-chromium
at 123.0.6312.122. Is it possible to un-bork this beloved port somehow, and
update?

thanks!
Comment 1 Mikael Urankar freebsd_committer freebsd_triage 2024-04-28 11:30:50 UTC 
snappy ABI has changed and dependent ports were not bumped, cc'ing vanilla
Comment 2 Dave Cottlehuber freebsd_committer freebsd_triage 2024-05-05 15:59:18 UTC 
fixed in ungoogled-chromium-124.0.6367.78 (built & tested locally)