glibc dependancy problem

[jury]

I have compiled some open source DOS game remake. When I try to run it, it complains that it needs glibc 2.34

Code: Select all

./abuse
./abuse: /lib64/libc.so.6: version `GLIBC_2.34' not found (required by ./abuse)

Salix 15 has version 2.33:

Code: Select all

jury[~]$ ldd --version
ldd (GNU libc) 2.33

So I decided to compile the newest glibc (its 2.40 now) but not to replace the system 2.33 but somewhere independently.
It compiled and installed fine to /home/jury/Downloads/installed/glibc-2.40/binary

So now when I try to run the above binary using freshly compiled glibc I get the message that my freshly compiled glibc 2.40 needs glibc 2.35:

Code: Select all

export LD_PRELOAD=/home/jury/Downloads/installed/glibc-2.40/binary/lib/libc.so.6
./abuse
./abuse: /lib64/ld-linux-x86-64.so.2: version `GLIBC_2.35' not found (required by /home/jury/Downloads/installed/glibc-2.40/binary/lib/libc.so.6)

I must fall into some dependancy hell, but I do not even understand above message. So, how can I run my ./abuse binary not messing with system glibc 2.33?

[gapan]

Hi jury.

Did you really compile that game? If so how? It seems that you only tried to use a precompiled binary and unfortunately, that binary was created on a system with a newer glibc than the one we have in Salix 15.0, so it won't work.

It is not possible to compile something and have the resulting binary depend on a glibc version newer than the one you have installed.

Upgrading glibc is not easy. I would not recommend even trying it.

But, what game is this exactly? Is it maybe this one? https://flathub.org/apps/com.github.Xenoveritas.abuse
If so, just installing the flatpak would be the easiest way to run it.

[jury]

But, what game is this exactly? Is it maybe this one? https://flathub.org/apps/com.github.Xenoveritas.abuse
If so, just installing the flatpak would be the easiest way to run it.

Yes, its this game, but the purpose is not to install it in Salix and play. I want to cross-compile it to my favourite, quite old, vintage platform. But I had some troubles running it on that platform (resources do not load even thou those are there) so I just want to compile it on a platform with nice gui debugger, to see what is going on there.

It is not possible to compile something and have the resulting binary depend on a glibc version newer than the one you have installed.

Geez, you are right. After reading the above, I went to sources and done "make clean", which I was sure I did before but it seems not (I did, but only on the sources for that vintage platform) Then, after compiling from scratch, the binary does not complain about missing higher version of glibc (it just crashes during loading of resources, so time for debugging now)

Thanks!

PS.
The binary complaining about low version of glibc was compiled by me two years ago on the distribution before Salix, which was rolling distro (my first, and probably last one) I just forgot to do that "make clean" when picking this "project" again after the break.

[gapan]

OK, now I'm intrigued. What is that vintage platform?

[jury]

Its last computer from Atari. Released in 1992 named Falcon 030. It has 2 processors, main Motorola 68030 running at 16MHz and DSP 56001 running at 32MHz. I have this machine upgraded to the max, so it has last Motorola CPU from 68k series which is 68060 overclocked at 95MHz, 256MB DIMM memory and new graphics card with better resolutions, more colors, better blitter ... Quite some power
And this is why I just love open source. You can pick it up, and do whatever you want with it, even port it to any, even most exotic platform. Beautiful.

[gapan]

Oh wow! I wasn't expecting that! The Falcon is one of my favorite machines of all time! Last time I used one was in a recording studio about 25 years ago, years after Atari had shut down and the Falcon was out of production. But it was running Cubase XT and it was managing all sorts of samplers, drum machines as well as 32 audio tracks on ADAT tapes along with a 32 track Alesis mixing console. I remember it also had an external 160GB SCSI drive, which was crazy for the time.

I'm very familiar with the 68060 too. I had written an assignment/presentation on its architecture and pipelining features during my MSc.