Re: Please import some patches for breakage in 2019Q4 (or verify it's gone in 2020Q1)

["Dr. Thomas Orgis" <thomas.orgis%uni-hamburg.de@localhost>]

Am Thu, 26 Mar 2020 15:28:51 +0000
schrieb nia <nia%NetBSD.org@localhost>: 

> I've committed a handful of these.

Thanks at lot! Could you tell me which ones so that I know which
patches to delete before attempting a next full build?

> Are you sure that fltk13 needs xcb?

It does link to libxcb, at least, on my Linux system. Maybe optional.
Is libxcb troublesome on some platforms? My attempt to re-try the
build with pkgsrc CVS on my desktop failed because pkgsrc decided to
build openssl as dependency and that now fails the PLIST check for me
as it decided to install things in lib64 instead of lib. I'm updating
my main system now for openssl so that the one from pkgsrc is not built
(hopefully). I hope I can get back to fltk some time later. My use case
never includes openssl from pkgsrc, so I hope it's OK I stick to my
scheme for testing, too.

I'm looking at my system-wide install if libftlk now.

$ readelf -d /usr/lib/libfltk.so.1.3 |grep NEEDED
 0x0000000000000001 (NEEDED)             Shared library: [libXrender.so.1]
 0x0000000000000001 (NEEDED)             Shared library: [libXcursor.so.1]
 0x0000000000000001 (NEEDED)             Shared library: [libXfixes.so.3]
 0x0000000000000001 (NEEDED)             Shared library: [libXext.so.6]
 0x0000000000000001 (NEEDED)             Shared library: [libpthread.so.0]
 0x0000000000000001 (NEEDED)             Shared library: [libdl.so.2]
 0x0000000000000001 (NEEDED)             Shared library: [libX11.so.6]
 0x0000000000000001 (NEEDED)             Shared library: [libm.so.6]
 0x0000000000000001 (NEEDED)             Shared library: [libstdc++.so.6]
 0x0000000000000001 (NEEDED)             Shared library: [libgcc_s.so.1]
 0x0000000000000001 (NEEDED)             Shared library: [libc.so.6]
$ readelf -d /usr/lib/libX11.so |grep NEEDED|grep xcb
 0x0000000000000001 (NEEDED)             Shared library: [libxcb.so.1]

So it enters the picture indirectly. Maybe it's not required as
direct dependency after all.

> needing it. I can see it clearly needs libXcursor and already
> committed that.
> 
> What's the PLIST issue you're seeing with qt5 with/without KMS?

It found libdrm on my host system and installed KMS stuff, triggering
PLIST failure because of unexpected files, AFAIR. I'll test that again
once my host system recovers from rebuilding things with openssl.


Alrighty then,

Thomas


-- 
Dr. Thomas Orgis
HPC @ Universität Hamburg