Re: Running 32-bit static exeutable on 64-bit Debian

[Van Snyder <van.snyder@sbcglobal.net>]

On Sat, 2024-07-20 at 09:31 +0200, Thomas Schmitt wrote:

Hi,

Van Snyder wrote:

And there's still the mystery why a statically-linked executable wants to

load a shared object library.

I doubt that it is possible to make a purely statical binary with no

references to .any so libraries.

(If it were generally possible, why then exist Flatpack and Snap ?)

Check by program "ldd" which dynamic dependencies the binary has:

  ldd ./LinuxSusser

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."

When I retry them, "file" says it's dynamically linked, and "ldd" reports about two dozen links to missing shared object libraries.

I installed the first of them (which had already existed in an amd64 version), forcing an i386 version:

# sudo apt install libgtk2.0-0:i386

Now, instead of simply refusing to run, or (the original "Command not found") it lists a bunch of missing gtk modules (atk-bridge, pixmap, adwaita), not missing shared object libraries. Where do I get the missing gtk modules?

The program is not a Debian package. I got it years ago (2006) in a zip file from the author, so I don't understand why it was statically linked a few hours ago. The file's time stamp hasn't changed.

Have a nice day :)

Thomas