Missing .so files for pre-built binaries

[komh]

Currently, some .so files are missing in pre-built binaries.

libiconv.so.2: os2emx-cross-toolchain-libiconv.tar.gz

libmpfr.so.4: os2emx-cross-toolchain-libmpfr.tar.gz

libfl.so.2: libfl.tar.gz

[dryeo]

Seems that i686-pc-os2-emx-ar depends on libfl.so.2 used by flex it seems, though not here.

i686-pc-os2-emx-ar: error while loading shared libraries: libfl.so.2: cannot open shared object file: No such file or directory

[komh]

Seems that i686-pc-os2-emx-ar depends on libfl.so.2 used by flex it seems, though not here.

i686-pc-os2-emx-ar: error while loading shared libraries: libfl.so.2: cannot open shared object file: No such file or directory

Added to the first comment.

[xhajt03]

Do I understand it correctly that having these would allow using the binaries directly on Debian oldstable (Bookworm)? I was able to use the binaries out of box on Debian stable (Trixie), but was missing some .so files on Bookworm.

[komh]

I think so, but if you have any troubles due to missing .so files, please report here. I'll provide the files.

[xhajt03]

When trying on Debian Bookworm, I get the following error when running the provided port of as:

/usr/lib/x86_64-linux-gnu/fpc/3.2.2/bin/os2/os2-as: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_ 2.38' not found (required by /usr/lib/x86_64-linux-gnu/fpc/3.2.2/bin/os2/os2-as)

(os2-as mentioned there is just a symlink to provide the name expected by FPC when cross-compiling to the os2 target)

[komh]

Here is the libc.so 2.39 file:

libc.tar.gz

However, I recommend to update the libc on your system with package manager instead of copying the above file. Just copying libc so file may cause unexpected behavior due to its dependencies.

[xhajt03]

I update the installed packages regularly, but a newer libc version is not included in these updates (not surprisingly - for the same reasons you outlined yourself above).

[xhajt03]

So the short update for this is - replacing / updating just the libc.so.6 file wouldn't help, it fails due to other dependencies (missing symbols). Not really a big deal, it just means that one needs the latest stable Debian version at least in order to use this port - not really an issue.

[dryeo]

The other and traditional option is rebuilding it so it matches your system exactly. If you really want to get fancy, could build a deb and post the spec file somewhere so KOMH could link to it.

[xhajt03]

Thanks, and yes, I'm aware I could try that. This isn't a show-stopper for me for sure (for multiple reasons - one being the fact that I have another environment where I can test it, another being that I intend to upgrade my Debian to the latest version sooner or later anyway, and finally, I could try to build it myself according to the provided documentation).

[komh]

I'll consider to make all the binaries static.