SliTaz Forum

tcll

Member

Registered: 2026-01-25

Posts: 31

comand not found (portable application)

Hey, I wasn't sure where to create this thread, but I just need some info about if glibc/ld.so is 64bit or not since that would create an issue like this...

I'm running SliTaz 5.0 from a while back using kernel [c]3.16.55-slitaz64[/c] which detects the machine type is actively x86_64, though I find it interesting the arch reports i486.

Going by that, I have a few hand-crafted appimages of some portable python 2015 (3.4.3) interpreters (from snapshot.debian.org) which I've been building all my userspace apps around

Since they use glibc 2.2.5, they should at least in theory work as far back as Linux 2.0, which the range of Slitaz kernels fall within...

Though when I try to run my 64bit appimage, [c]stat64()[/c] seems to return [c]-1 ENOENT (No such file or directory)[/c] (although [c]clone()[/c] seems to attach and immediately fail) while the AppRun that launches it fails with [c]python3.4m: command not found[/c]

I've tested these interpreters on every other machine I have, with a wide range of distros from Zorin (2012), Xubuntu 16.04(.2 32bit, .3 64bit), Void Linux (various kernels 2018-2020), Artix (various kernels 2017-2022), Mint, and even Kali Linux (old version), and they run just fine on every one of those.

So I think something's up with the libraries of SliTaz somewhere, and would like to know if it's fixable

I've already ripped out quite a few things from /usr/lib including dbus and polkit, as well as a bunch of bloat (fixing my system's boot in the process, removed a ton of services as init is too dependant)

So don't expect me to be able to use GCC to compile anything as I've probably broken that as well at this point XD

But regardless, I should be able to remove everything from /usr/lib outside of glibc itself and python should still be able to run

I haven't quite gotten low enough yet where I can have a portable libc included like qtox has with musl, but it should theoretically be doable as kernel syscalls are much more stable than libc...

Again though, I just need info on what slitaz's glibc expects that could be breaking this

shann

Administrator

Registered: 2011-04-01

Posts: 1,296

Website

Re: comand not found (portable application)

Hi tcll,

For SliTaz 5.0, userland remain 32 bit, only kernel is purpose to both 32 bit (linux package) or 64 bit (linux64 package).

That's why you see x86_64 machine but arch report i486

When you boot, iso choose right kernel depend of ram capacity.

If understand your appimage is targeted for x86_64 architecture, in case not sure could be work properly and explain error you see.

I purpose if you can, try version i build that fully x86_64 (kernel and userland).

https://people.slitaz.org/~shann/slitaz-current64-stuff/isos/slitaz-6.0-core64-grub2.iso

At begin i call it "current64", to avoid confusing with rolling/cooking version, i name it 6.0

Hope that your apps work as expected, i more confident, my brother use laptop for media center with Molotov app (on website, it's provided as appimage)

tcll

Member

Registered: 2026-01-25

Posts: 31

Re: comand not found (portable application)

Ah I see, so my thoughts were correct then, thanks for letting me know

I wonder if I can't frankenstein something from the 6.0 x64 binaries on the 5.0 kernel to get something running

That'd certainly be fun XD

Not like I haven't already done something similar with Artix using 2017 binaries with a 2022 kernel and libc XD

But I should be able to get things working as is already then if I just nab my 32bit python

Thanks again

shann

Administrator

Registered: 2011-04-01

Posts: 1,296

Website

Re: comand not found (portable application)

I don't doing test but yes normally you can use 6.0 x64 binaries with 5.0 kernel (3.16.55-linux64), glibc of 6.0 is built with "--enable-kernel=3.16.55".

6.0 x86_64 is not multilib, you can't run both x86 / x86_64 binaries.

But if you have 32bit chroot, he can run without problem.

If you want keep fully 32bit, on rolling/cooking you have also python3 (python 3.8.3 to be exactly).

https://pkgs.slitaz.org/?package=python3

Python3 not installed by default, could be installed with this [c]tazpkg -gi python3[/c]

tcll

Member

Registered: 2026-01-25

Posts: 31

Re: comand not found (portable application)

Oh hmm, I'll keep that in mind then, thanks for letting me know

And nah, it's fine, my goal is to basically get down to kernel only (and modules) for whatever is in [c]/*[/c], so all my apps are pretty much already in their own loose chroot (just isolated (no ref outside of programdir aside from potential Gnome or GNU libs) env vars with [c]AppRun[/c])

All my apps are just portable (GNU has pushed me great lengths for this), so I can run them off a flash drive if I so choose on any kernel without issues

(Yes, the exact stuff everyone propagandizes isn't possible is exactly what I'm doing)

I'll just have to figure out how to include libc if I want compatibility to work nicely

(I can probably even use Debian's 2015 glibc just to keep everything sane (same source))

Which tbh is something I've been wanting to figure out, just haven't had the ability to play around with (opportunity is now near)

[c]#linuxsucks2026[/c] XD

(I love Linux, but don't love GNU and everything else that follows [c]#breakeverything[/c], in fact am working on stripping away libc from python entirely (modifying machine code) so it can run on all kernels)

tcll

Member

Registered: 2026-01-25

Posts: 31

Re: comand not found (portable application)

hmmmmmm... What would be lost if I had a little fun and got greedy with glibc 2.3.2?? :smirk:

I took a look at glibc 2.2.5 (the lowest my python version supports) and it seems that version is only 32bit, so I looked at the first 64bit version I could find...

I also took a look and noticed SliTaz used glibc 2.14.1 (32bit)

So I'm just curious what if any potential problems I'd be causing if I overrode that with a much earlier version

I noticed you used very few extensions as well, so I highly doubt I'll cause much... I'm just being cautious with my bullheadedness as this is unexplored territory for me XD

(I intend to clean up these messes later when I edit machine code (heck I'm already removing TCL from all my toys now that I can use [c]/tmp/.X11-unix/X0[/c] (really need a better way to find this) directly), it's just what I have to put up with atm)

tcll

Member

Registered: 2026-01-25

Posts: 31

Re: comand not found (portable application)

Just some minor insight, not gonna get annoying about this XD

But for some tests with that very lib in question, it seems to work properly on my Artix machine which has a WAY higher glibc version

though of course running it with a 64bit strace is now holding me back (pay no attention to my table flipping) XD

Anyways, I expect it'll work the same when I get this over to SliTaz

[attachment=53669,3795]