Does pcretest start, or does it fail in the same way? Can you post output of "objdump -p /usr/local/lib/libpcre.so.3.0" please? I guess "ls -l /usr/local/lib" might give some clues too.
On 2020/04/23 20:04, Jay Hart wrote: > Here is the output... > > Script started on Thu Apr 23 19:37:38 2020 > ld.so loading: 'mc' > exe load offset: 0x18c50000 > flags mc = 0x0 > head mc > obj mc has mc as head > examining: 'mc' > loading: libintl.so.6.0 required by mc > flags /usr/local/lib/libintl.so.6.0 = 0x0 > obj /usr/local/lib/libintl.so.6.0 has mc as head > loading: libc.so.95.1 required by mc > flags /usr/lib/libc.so.95.1 = 0x20 > obj /usr/lib/libc.so.95.1 has mc as head > loading: libssh2.so.9.0 required by mc > flags /usr/local/lib/libssh2.so.9.0 = 0x0 > obj /usr/local/lib/libssh2.so.9.0 has mc as head > loading: libslang.so.16.0 required by mc > flags /usr/local/lib/libslang.so.16.0 = 0x0 > obj /usr/local/lib/libslang.so.16.0 has mc as head > loading: libpthread.so.26.1 required by mc > flags /usr/lib/libpthread.so.26.1 = 0x8 > obj /usr/lib/libpthread.so.26.1 has mc as head > loading: libssl.so.47.6 required by mc > flags /usr/lib/libssl.so.47.6 = 0x0 > obj /usr/lib/libssl.so.47.6 has mc as head > loading: libgmodule-2.0.so.4200.9 required by mc > flags /usr/local/lib/libgmodule-2.0.so.4200.9 = 0x88 > obj /usr/local/lib/libgmodule-2.0.so.4200.9 has mc as head > loading: libcrypto.so.45.5 required by mc > flags /usr/lib/libcrypto.so.45.5 = 0x0 > obj /usr/lib/libcrypto.so.45.5 has mc as head > loading: libm.so.10.1 required by mc > flags /usr/lib/libm.so.10.1 = 0x0 > obj /usr/lib/libm.so.10.1 has mc as head > loading: libz.so.5.0 required by mc > flags /usr/lib/libz.so.5.0 = 0x0 > obj /usr/lib/libz.so.5.0 has mc as head > loading: libcurses.so.14.0 required by mc > flags /usr/lib/libcurses.so.14.0 = 0x0 > obj /usr/lib/libcurses.so.14.0 has mc as head > loading: libutil.so.13.1 required by mc > flags /usr/lib/libutil.so.13.1 = 0x0 > obj /usr/lib/libutil.so.13.1 has mc as head > loading: libglib-2.0.so.4201.2 required by mc > flags /usr/local/lib/libglib-2.0.so.4201.2 = 0x8 > obj /usr/local/lib/libglib-2.0.so.4201.2 has mc as head > loading: libiconv.so.7.0 required by mc > flags /usr/local/lib/libiconv.so.7.0 = 0x0 > obj /usr/local/lib/libiconv.so.7.0 has mc as head > linking dep /usr/lib/libcurses.so.14.0 as child of mc > linking dep /usr/lib/libm.so.10.1 as child of mc > linking dep /usr/lib/libutil.so.13.1 as child of mc > linking dep /usr/lib/libssl.so.47.6 as child of mc > linking dep /usr/lib/libcrypto.so.45.5 as child of mc > linking dep /usr/lib/libz.so.5.0 as child of mc > linking dep /usr/local/lib/libslang.so.16.0 as child of mc > linking dep /usr/local/lib/libssh2.so.9.0 as child of mc > objname /usr/local/lib/libgmodule-2.0.so.4200.9 is nodelete > linking dep /usr/local/lib/libgmodule-2.0.so.4200.9 as child of mc > linking dep /usr/local/lib/libintl.so.6.0 as child of mc > linking dep /usr/local/lib/libglib-2.0.so.4201.2 as child of mc > linking dep /usr/local/lib/libiconv.so.7.0 as child of mc > linking dep /usr/lib/libpthread.so.26.1 as child of mc > linking dep /usr/lib/libc.so.95.1 as child of mc > examining: '/usr/lib/libcurses.so.14.0' > examining: '/usr/lib/libm.so.10.1' > examining: '/usr/lib/libutil.so.13.1' > examining: '/usr/lib/libssl.so.47.6' > loading: libcrypto.so.45.5 required by /usr/lib/libssl.so.47.6 > linking dep /usr/lib/libcrypto.so.45.5 as child of /usr/lib/libssl.so.47.6 > examining: '/usr/lib/libcrypto.so.45.5' > examining: '/usr/lib/libz.so.5.0' > examining: '/usr/local/lib/libslang.so.16.0' > examining: '/usr/local/lib/libssh2.so.9.0' > loading: libcrypto.so.45.5 required by /usr/local/lib/libssh2.so.9.0 > loading: libz.so.5.0 required by /usr/local/lib/libssh2.so.9.0 > loading: libssl.so.47.6 required by /usr/local/lib/libssh2.so.9.0 > linking dep /usr/lib/libssl.so.47.6 as child of /usr/local/lib/libssh2.so.9.0 > linking dep /usr/lib/libcrypto.so.45.5 as child of > /usr/local/lib/libssh2.so.9.0 > linking dep /usr/lib/libz.so.5.0 as child of /usr/local/lib/libssh2.so.9.0 > examining: '/usr/local/lib/libgmodule-2.0.so.4200.9' > loading: libglib-2.0.so.4201.2 required by > /usr/local/lib/libgmodule-2.0.so.4200.9 > linking dep /usr/local/lib/libglib-2.0.so.4201.2 as child of > /usr/local/lib/libgmodule-2.0.so.4200.9 > examining: '/usr/local/lib/libintl.so.6.0' > loading: libiconv.so.7.0 required by /usr/local/lib/libintl.so.6.0 > linking dep /usr/local/lib/libiconv.so.7.0 as child of > /usr/local/lib/libintl.so.6.0 > examining: '/usr/local/lib/libglib-2.0.so.4201.2' > loading: libpthread.so.26.1 required by /usr/local/lib/libglib-2.0.so.4201.2 > loading: libiconv.so.7.0 required by /usr/local/lib/libglib-2.0.so.4201.2 > loading: libpcre.so.3.0 required by /usr/local/lib/libglib-2.0.so.4201.2 > ld.so: mc: can't load library 'libpcre.so.3.0' > Killed > > Script done on Thu Apr 23 19:37:39 2020 > > > > > Stuart, > > > > I'm working on capturing the output. I think I see why you say it needs to > > run in a script. > > > > Thanks for the help! > > > > Jay > > > >> On 2020-04-23, Raf Czlonka <rczlo...@gmail.com> wrote: > >>> Would this by any chance be related to the fact that pcre has been > >>> removed from WANTLIB[0][1] but the package still pulls in libpcre? > >>> > >>> $ ldd /usr/local/bin/mc | grep pcre > >>> 00001b530c236000 00001b530c27c000 rlib 0 1 0 > >>> /usr/local/lib/libpcre.so.3.0 > >> > >> ldd shows indirect dependencies too, see "objdump -p /usr/local/bin/mc | > >> grep NEEDED" for the direct dep's. > >> > >> in this case pcre is pulled in by glib2, an excerpt from a working run with > >> LD_DEBUG set: > >> > >> ... > >> linking dep /usr/local/lib/libglib-2.0.so.4201.3 as child of > >> /usr/local/lib/libgmodule-2.0.so.4200.10 > >> examining: '/usr/local/lib/libglib-2.0.so.4201.3' > >> loading: libiconv.so.7.0 required by /usr/local/lib/libglib-2.0.so.4201.3 > >> loading: libpcre.so.3.0 required by /usr/local/lib/libglib-2.0.so.4201.3 > >> flags /usr/local/lib/libpcre.so.3.0 = 0x0 > >> obj /usr/local/lib/libpcre.so.3.0 has mc as head > >> ... > >> > >> if we are to have any hope of figuring out what happened, OP will need > >> to provide the debug output. the most common cause would be an incomplete > >> update.. > >> > >> > >> > > > > > > > >
