On Sat, Jul 20, 2024 at 01:15:22 -0700, Van Snyder wrote: > > Van Snyder wrote: > > > And there's still the mystery why a statically-linked executable > > > wants to > > > load a shared object library.
https://manpages.debian.org/bookworm/manpages-dev/dlopen.3.en.html > Am I losing my mind? > > At first I had done "file LinuxSusser". It reported "Statically > linked." > > Just to be sure, I did the recommended "ldd LinuxSusser." It also > reported Statically linked." Then it's almost certainly using dlopen() to load this shared library. The unpleasant part is that once you install this 32-bit shared lib, you'll get past this one dlopen() call, and then there might be more of them. You'll just have to whittle it down piece by piece until it stops crashing. There's no way to get a complete list all at once. Your testing will also have to try to cover as many code paths as possible. Maybe there's a shared lib that only gets read when you activate a specific feature in the program. You'll have to try to test as many features as you can, before you can be reasonably sure you've got all the libs it will want.
