Re: [gentoo-user] Keeping 17-year-old Kylix software alive
Den 09.06.2019 11:24, skrev Matthias Hanft: The old Kylix libraries just do some comprehensive calculations. Not too difficult to manually translate that into PHP (or any other script language, or even plain C), but just hundreds of code lines to type... Find a Pascal-to-C++ translator program, and/or hire a college student over the summer to do it.
Re: [gentoo-user] Keeping 17-year-old Kylix software alive
Mick wrote: > > Did you try the new revdep-rebuild in case it works (better)? "Dynamic linking on your system is consistent... All done." which, obviously, is not true :-) BTW, the old revdep-rebuild.sh finally wants to rebuild hundreds of packages... which I interrupted - makes no sense at all for me. > I am not familiar with the particular software and wouldn't know how to keep > it alive on a present day Gentoo system - other than building Gentoo using an > old snapshot and installation media, perhaps in a VM and using additional > packages of the same era from the attic in a local overlay. Ok, I could set up a complete "old" system, of course, but I'm using the old libraries on a "production system" (they are called by a PHP extension which is used by a public accessible Apache web server). So I'm really interested in keeping the rest of the system up-to-date. The old Kylix libraries just do some comprehensive calculations. Not too difficult to manually translate that into PHP (or any other script language, or even plain C), but just hundreds of code lines to type... > Someone else may be able to offer useful advice, but I would think this is > more of a question suitable for the gentoo-dev mailing list[1] and IRC > channel[2]. Have you tried asking there? Not yet - AFAIK the gentoo-dev list is read-only for non-developpers, and I've never used IRC in my life at all :-) But I'll give it a try if I have no further ideas... -Matt
Re: [gentoo-user] Keeping 17-year-old Kylix software alive
On Sunday, 9 June 2019 09:21:17 BST Mick wrote:
> Hi Matt,
>
> On Sunday, 9 June 2019 08:49:21 BST Matthias Hanft wrote:
> > 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).
>
> Did you try the new revdep-rebuild in case it works (better)?
>
> > 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
>
> I am not familiar with the particular software and wouldn't know how to keep
> it alive on a present day Gentoo system - other than building Gentoo using
> an old snapshot and installation media, perhaps in a VM and using
> additional packages of the same era from the attic in a local overlay.
>
> Someone else may be able to offer useful advice, but I would think this is
> more of a question suitable for the gentoo-dev mailing list[1] and IRC
> channel[2]. Have you tried asking there?
>
> [1] https://www.gentoo.org/get-involved/mailing-lists
> [2] https://www.gentoo.org/get-involved/irc-channels/all-channels.html
Hmm ... reading about borland kylix in the link you provided and this article
I'm wondering if the two are related:
https://www.gentoo.org/support/news-items/2017-04-10-split-and-slotted-wine.html
--
Regards,
Mick
signature.asc
Description: This is a digitally signed message part.
Re: [gentoo-user] Keeping 17-year-old Kylix software alive
Hi Matt,
On Sunday, 9 June 2019 08:49:21 BST Matthias Hanft wrote:
> 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).
Did you try the new revdep-rebuild in case it works (better)?
> 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
I am not familiar with the particular software and wouldn't know how to keep
it alive on a present day Gentoo system - other than building Gentoo using an
old snapshot and installation media, perhaps in a VM and using additional
packages of the same era from the attic in a local overlay.
Someone else may be able to offer useful advice, but I would think this is
more of a question suitable for the gentoo-dev mailing list[1] and IRC
channel[2]. Have you tried asking there?
[1] https://www.gentoo.org/get-involved/mailing-lists
[2] https://www.gentoo.org/get-involved/irc-channels/all-channels.html
--
Regards,
Mick
signature.asc
Description: This is a digitally signed message part.
[gentoo-user] Keeping 17-year-old Kylix software alive
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
