On Sun, Apr 7, 2024 at 3:52 AM Damjan Jovanovic <dam...@apache.org> wrote:
> > > On Sat, Apr 6, 2024 at 9:30 PM Pedro Lino <pedro.l...@mailbox.org.invalid> > wrote: > >> Hi Damjan >> >> > On 04/06/2024 4:08 PM WEST Damjan Jovanovic <dam...@apache.org> wrote: >> >> > openoffice-maps.txt was for the shell script that launches AOO, and >> > openoffice-maps2.txt was for AOO itself. >> >> I'm glad I sent both :) >> >> > In openoffice-maps2.txt I don't see libucpdav1.so (the WebDAV >> component) in >> > memory at all, which is highly unusual. >> > >> > Please find libucpdav1.so in your AOO installation, probably under >> > /opt/openoffice4/programs, and then run these: >> > ldd libucpdav1.so >> > readelf -d libucpdav1.so >> > and post the output. >> >> Thank you again for your patience and instructions! >> Please find two files attached >> >> > This: > libssl.so.3 => not found > libcrypto.so.3 => not found > is a serious problem. > > Something has managed to link to OpenSSL dynamically instead of > statically, causing a hard dependency on the underlying Linux distro to > have OpenSSL 3. > > Since your older Linux doesn't have OpenSSL 3 yet, modules that need it, > can't even load. > > And having installed that Linux nightly build myself, here is the culprit: > > ---snip--- > $ readelf -d libcurl.so.4 > > Dynamic section at offset 0x72d40 contains 30 entries: > Tag Type Name/Value > 0x0000000000000001 (NEEDED) Shared library: [libidn2.so.0] > > > * 0x0000000000000001 (NEEDED) Shared library: > [libssl.so.3] 0x0000000000000001 (NEEDED) Shared library: > [libcrypto.so.3]* 0x0000000000000001 (NEEDED) Shared library: > [libz.so.1] > 0x0000000000000001 (NEEDED) Shared library: [libpthread.so.0] > 0x0000000000000001 (NEEDED) Shared library: [libc.so.6] > 0x000000000000000e (SONAME) Library soname: [libcurl.so.4] > ---snip--- > > Curl has started linking to OpenSSL dynamically instead of statically, > probably a result of our recent OpenSSL upgrade, and thus became dependent > on the Linux distribution having OpenSSL 3. > > Let me investigate where Curl goes wrong... > I'll be starting a separate thread to discuss the problem with Curl that I found. Regards Damjan
