[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"
- Reply: bugzilla-noreply_a_freebsd.org: "[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""
- Reply: bugzilla-noreply_a_freebsd.org: "[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""
- Reply: bugzilla-noreply_a_freebsd.org: "[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""
- Reply: bugzilla-noreply_a_freebsd.org: "[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""
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 19 Apr 2024 15:33:32 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278464 Bug ID: 278464 Summary: www/ungoogled-chromium: 119.0.6045.199 fails to start: ld-elf.so.1: /usr/local/share/ungoogled-chromium/ungoogled-chromium : Undefined symbol "_ZN6snappy11RawCompressEPKcmPcPm" Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Ports Framework Assignee: portmgr@FreeBSD.org Reporter: dch@freebsd.org CC: ports-bugs@FreeBSD.org 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! -- You are receiving this mail because: You are on the CC list for the bug.