[gentoo-user] Keeping 17-year-old Kylix software alive

[Matthias Hanft]

Hi,

many years ago, I created some libSomething.so with Kylix 3 (1)
which still worked with current (32bit) Gentoo systems (Kernel
4.14.83).

Using "revdep-rebuild.sh" (the *old* script!), for some time,
I already got messages like

broken /usr/local/lib/libxercesxmldom.so.1
/usr/local/lib/libxercesxmldom.so.1 (symbol __pthread_atfork version GLIBC_2.0 not defined in file libpthread.so.0 with link time reference
symbol __pthread_initialize version GLIBC_2.0 not defined in file libpthread.so.0 with link time reference)

but everything worked fine anyway ("libxercesxmldom" is part of
Borland's standard runtime libraries).

However, after upgrading glibc from 2.27 to 2.28 (or newer), this
is not true any more: Compiling and running a C program using the
old Kylix libSomething.so libraries causes Segmentation fault, and
Apache using a PHP extension which calls those libraries won't start
at all any more.

For recompiling the Kylix libSomething.so libraries, I'm keeping
alive a Suse 8.1 Linux (2) in VirtualBox (Kernel 2.4.19).

Do you see any chance to keep those Kylix libraries alive and
running? If it would help, I'd try to install the old Kylix on
a current Gentoo system and try to recompile there (although
I guess Kylix won't run on a current Kernel any more - if it
can be installed at all).

Switching to another (Pascal-/Delphi-/Lazarus-/etc.) Compiler
is not an option because the .so libraries are in fact "packages"
(BPL, a special Borland library version).

Is there any possibility for some "binary interface/gateway" to
use those libraries any more, or do I have to reprogram the
whole functionality with PHP?

-Matt

(1) https://en.wikipedia.org/wiki/Borland_Kylix
(2) https://en.wikipedia.org/wiki/SUSE_Linux#SUSE_distributions