[Bug 285401] x11/libxkbcommon: after recent updates to 1.8.0 and 1.8.1 several ports may need a PORTREVISION bump
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 19 Mar 2025 00:58:37 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285401 --- Comment #38 from John Hein <jcfyecrayz@liamekaens.com> --- devel/dbus has the same problem (this is stable/13 from January with clang 19.1.5): ====================== Command line: `cc /usr/ports/devel/dbus/work/dbus-1.16.2/_build/meson-private/tmp1l5v4yhu/testfile.c -o /usr/ports/devel/dbus/work/dbus-1.16.2/_build/meson-private/tmp1l5v4yhu/output.exe -O2 -pipe -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing -isystem /usr/local/include -D_FILE_OFFSET_BITS=64 -O0 -Werror=implicit-function-declaration -Wl,--fatal-warnings -Wl,--version-script,/usr/ports/devel/dbus/work/dbus-1.16.2/dbus/test-version-script` -> 1 stderr: ld: error: non-exported symbol 'environ' in '/usr/lib/crt1.o' is referenced by DSO '/lib/libc.so.7' ld: error: non-exported symbol '__progname' in '/usr/lib/crt1.o' is referenced by DSO '/lib/libc.so.7' cc: error: linker command failed with exit code 1 (use -v to see invocation) ----------- Compiler for C supports link arguments -Wl,--version-script,/usr/ports/devel/dbus/work/dbus-1.16.2/dbus/test-version-script: NO ====================== I noticed this when I built net-im/folks which depends on a number of ports that link with libdbus (also uses a meson test) - if those other ports were not rebuilt, but libdbus was, then the get errors like: /usr/local/lib/libdbus-1.so.3: version LIBDBUS_1_3 required by /usr/local/lib/libgconf-2.so.4 not defined There are likely going to be other cases of this where version-script support is incorrectly detected as unsupported. I'm just mentioning it in this bug because of the similarity (and to add to the wider context for more perspective about the best way to fix this). As I mentioned in bug 281440, it would be beneficial to add to the ports QA testing to check before / after ABI changes to have the maintainer / committer aware of unintentional ABI changes like this before they are committed. -- You are receiving this mail because: You are the assignee for the bug.