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

2024-07-20 Thread Nicholas Geovanis
On Sat, Jul 20, 2024, 8:57 AM Greg Wooledge wrote: > 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/bo

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

2024-07-20 Thread Thomas Schmitt
Hi, Greg Wooledge wrote: > Then it's almost certainly using dlopen() to load this shared library. dlopen(3) explains the missing gtk modules which (i assume) are not reported by ldd. But it does not explain why "file" and ldd now report something different than they reported a while ago. Have a

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

2024-07-20 Thread Greg Wooledge
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? > >

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

2024-07-20 Thread Jeffrey Walton
On Sat, Jul 20, 2024 at 5:50 AM Thomas Schmitt wrote: > > 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. >

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

2024-07-20 Thread Thomas Schmitt
Hi, Van Snyder wrote: > Am I losing my mind? Since this could mean a fatal end to the endeavor to run your program we should postpone this hypothesis until nearly everything else is outruled. > At first I had done "file LinuxSusser". It reported "Statically linked." > Just to be sure, I did the

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

2024-07-20 Thread Van Snyder
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

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

2024-07-20 Thread Thomas Schmitt
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

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

2024-07-20 Thread David
On Sat, 20 Jul 2024 at 06:44, Van Snyder wrote: > On Sat, 2024-07-20 at 05:54 +, David wrote: > > On Sat, 20 Jul 2024 at 04:56, Van Snyder wrote: > > > I'm trying to run a 32-bit static executable on 64-bit Debian 12.5 > > > "bookworm." > > > > > > When I launch it, I get > > > > > > ./Linu

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

2024-07-19 Thread Van Snyder
On Sat, 2024-07-20 at 05:54 +, David wrote: > On Sat, 20 Jul 2024 at 04:56, Van Snyder > wrote: > > > I'm trying to run a 32-bit static executable on 64-bit Debian 12.5 > > "bookworm." > > > > When I launch it, I get > > > > ./LinuxSusser: error while loading shared libraries: libgtk-x11- >

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

2024-07-19 Thread David
On Sat, 20 Jul 2024 at 04:56, Van Snyder wrote: > I'm trying to run a 32-bit static executable on 64-bit Debian 12.5 "bookworm." > > When I launch it, I get > > ./LinuxSusser: error while loading shared libraries: libgtk-x11-2.0.so.0: > cannot open shared object file: No such file or directory