On my Ubuntu box, when I link against libpango, I get:
$ lddtree mrv2
...
libpango-1.0.so.0 => /lib/x86_64-linux-gnu/libpango-1.0.so.0
libgio-2.0.so.0 => /lib/x86_64-linux-gnu/libgio-2.0.so.0
libgmodule-2.0.so.0 =>
/lib/x86_64-linux-gnu/libgmodule-2.0.so.0
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1
libmount.so.1 => /lib/x86_64-linux-gnu/libmount.so.1
libblkid.so.1 => /lib/x86_64-linux-gnu/libblkid.so.1
libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1
<=========== why?
libpcre2-8.so.0 => /lib/x86_64-linux-gnu/libpcre2-8.so.0
libfribidi.so.0 => /lib/x86_64-linux-gnu/libfribidi.so.0
libthai.so.0 => /lib/x86_64-linux-gnu/libthai.so.0
libdatrie.so.1 => /lib/x86_64-linux-gnu/libdatrie.so.1
libharfbuzz.so.0 => /lib/x86_64-linux-gnu/libharfbuzz.so.0
libfreetype.so.6 => /lib/x86_64-linux-gnu/libfreetype.so.6
libpng16.so.16 => /lib/x86_64-linux-gnu/libpng16.so.16
libbrotlidec.so.1 =>
/lib/x86_64-linux-gnu/libbrotlidec.so.1
libbrotlicommon.so.1 =>
/lib/x86_64-linux-gnu/libbrotlicommon.so.1
libgraphite2.so.3 => /lib/x86_64-linux-gnu/libgraphite2.so.3
...
On Rocky 8.1, libpango does not link against libgio-2.0, accordint to
lddtree, but I still get:
$ lddtree mrv2
..
libgio-2.0.so.0 => /lib/x86_64-linux-gnu/libgio-2.0.so.0
libmount.so.1 => /lib/x86_64-linux-gnu/libmount.so.1
libblkid.so.1 => /lib/x86_64-linux-gnu/libblkid.so.1
libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1
libpcre2-8.so.0 => /lib/x86_64-linux-gnu/libpcre2-8.so.0
...
Where does libgeo-2 and more important libselinux come from? Can I
avoid them? Are they the result of linking against wayland by any chance?
--
Gonzalo Garramuño
ggar...@gmail.com