On 2025-03-04 20:18, Harry Schmalzbauer wrote:
On 2025-03-04 18:05, Gleb Popov wrote:
On Tue, Mar 4, 2025 at 7:44 PM Harry Schmalzbauer
<[email protected]> wrote:
Is my base polluted?
My understanding is that something in flac uses the libgcc_s.so
library. Despite the name, this library is not specific to GCC and we
have an alternative implementation (coming from the LLVM project) in
our base. At the same time, any gcc package also installs a library
with the same name. Since you aren't running pkgbase, pkg only knows
about libgcc_s.so.1 that comes from gcc. It has no idea that another
library exists so it is safe to remove gcc without forcing flac
removal.
I'm not sure what to do about this, though. Maybe Baptiste will help us.
Thanks for the conclusion.
I was unsure if base llvm does provide libgcc_s.so.1 (legally).
But I don't see base libgcc_s.so.1 beeing utilized by audio/flac.
Anyways, until recently, shared libraries from base were filtered:
...
Contributing to the shlibs problem with pkg-2.x is beyond my scope, time
& skill wise...
And there's another unfortunate change:
The FreeBSD_version in "Annotations" isn't derived from ${OSVERSION}
anymore.
I pre-defined OSVERSION because of this pointless warning:
pkg instal check
Updating localrepo_x86-64-v3 repository catalogue...
Fetching meta.conf: 100% 179 B 0.2kB/s 00:01
Fetching data.pkg: 100% 576 KiB 589.3kB/s 00:01
Processing entries: 93%
Newer FreeBSD version for package check:
To ignore this error set IGNORE_OSVERSION=yes
- package: 1402504
- running userland: 1402501
Ignore the mismatch and continue? [y/N]:
The stable branch explicitly maintains ABI compatibility.
As far as I understand, it makes no sense for pkg(1) to check anything
else than the first two digits of $OSVERSION.
But I prepared a patch for the minor version mismatch problem:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285194
-harry
