> Now to track down what's sourcing that "libpcre.so.1 =>
> /usr/lib64/libpcre.so.1"
looks like it's getting pulled in by libselinux & libsystemd ...
for l in $(ldd ./haproxy | awk '{print $3}')
do
echo -e "LIB: ${l}"
ldd ${l} | grep libpcre
done
LIB: /lib64/libcrypt.so.1
LIB: /lib64/libdl.so.2
LIB: /lib64/libpthread.so.0
LIB: /usr/local/openssl11/lib64/libssl.so.1.1
LIB: /usr/local/openssl11/lib64/libcrypto.so.1.1
!!! LIB: /usr/lib64/libsystemd.so.0
!!! libpcre.so.1 => /usr/lib64/libpcre.so.1 (0x00007f8ceaf40000)
LIB: /usr/local/lib64/libpcre2-8.so.0
LIB: /usr/local/lib64/libpcre2-posix.so.2
libpcre2-8.so.0 => /usr/local/lib64/libpcre2-8.so.0
(0x00007fc22474f000)
LIB: /lib64/libc.so.6
LIB: /lib64/libresolv.so.2
!!! LIB: /lib64/libselinux.so.1
!!! libpcre.so.1 => /usr/lib64/libpcre.so.1 (0x00007f0d94f13000)
LIB: /usr/lib64/libcap.so.2
LIB: /lib64/librt.so.1
LIB: /usr/lib64/liblzma.so.5
LIB: /usr/lib64/liblz4.so.1
LIB: /usr/lib64/libgcrypt.so.20
LIB: /usr/lib64/libgpg-error.so.0
LIB: /usr/lib64/libpcre.so.1
whether or not that's causing the -vv 'artifact' or not, dunno yet
