Still haven't tried actually running it, but I've noticed that the executable depends on quite a lot of dynamic libraries.
Click here to view the secret text
×./drod5.2Linux: /lib64/libcurl.so.4: no version information available (required by ./drod5.2Linux)
linux-vdso.so.1 (0x00007fa42872c000)
libSDL2_mixer-2.0.so.0 => /lib64/libSDL2_mixer-2.0.so.0 (0x00007fa4286bb000)
libSDL2_ttf-2.0.so.0 => /lib64/libSDL2_ttf-2.0.so.0 (0x00007fa4286a5000)
libtheora.so.1 => not found
libvorbis.so.0 => /lib64/libvorbis.so.0 (0x00007fa428673000)
libogg.so.0 => /lib64/libogg.so.0 (0x00007fa428669000)
libjpeg.so.62 => /lib64/libjpeg.so.62 (0x00007fa4285cb000)
libmk4.so => not found
libpng16.so.16 => /lib64/libpng16.so.16 (0x00007fa428590000)
libcurl.so.4 => /lib64/libcurl.so.4 (0x00007fa4284ed000)
libexpat.so.1 => /lib64/libexpat.so.1 (0x00007fa4284c3000)
libjsoncpp.so.26 => not found
libz.so.1 => /lib64/libz.so.1 (0x00007fa42849f000)
libSDL2-2.0.so.0 => /lib64/libSDL2-2.0.so.0 (0x00007fa4282cb000)
libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007fa428000000)
libm.so.6 => /lib64/libm.so.6 (0x00007fa427f1a000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007fa42829a000)
libc.so.6 => /lib64/libc.so.6 (0x00007fa427d26000)
libharfbuzz.so.0 => /lib64/libharfbuzz.so.0 (0x00007fa427c0a000)
libfreetype.so.6 => /lib64/libfreetype.so.6 (0x00007fa427b3f000)
libnghttp2.so.14 => /lib64/libnghttp2.so.14 (0x00007fa42826d000)
libidn2.so.0 => /lib64/libidn2.so.0 (0x00007fa427aee000)
libssl.so.3 => /lib64/libssl.so.3 (0x00007fa427a16000)
libcrypto.so.3 => /lib64/libcrypto.so.3 (0x00007fa427400000)
libgssapi_krb5.so.2 => /lib64/libgssapi_krb5.so.2 (0x00007fa4279c1000)
/nix/store/lmn7lwydprqibdkghw7wgcn21yhllz13-glibc-2.40-66/lib/ld-linux-x86-64.so.2 => /lib64/ld-linux-x86-64.so.2 (0x00007fa42872e000)
libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x00007fa4272b1000)
libgraphite2.so.3 => /lib64/libgraphite2.so.3 (0x00007fa4279a1000)
libbz2.so.1 => /lib64/libbz2.so.1 (0x00007fa42798d000)
libbrotlidec.so.1 => /lib64/libbrotlidec.so.1 (0x00007fa42797f000)
libunistring.so.5 => /lib64/libunistring.so.5 (0x00007fa427104000)
libkrb5.so.3 => /lib64/libkrb5.so.3 (0x00007fa4278b5000)
libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x00007fa4270ed000)
libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00007fa4270e6000)
libkrb5support.so.0 => /lib64/libkrb5support.so.0 (0x00007fa4270d6000)
libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00007fa4270cf000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x00007fa4270bc000)
libpcre2-8.so.0 => /lib64/libpcre2-8.so.0 (0x00007fa42701c000)
libbrotlicommon.so.1 => /lib64/libbrotlicommon.so.1 (0x00007fa426ff9000)
libselinux.so.1 => /lib64/libselinux.so.1 (0x00007fa426fca000)
Among those the most concerning is libmk4.so (metakit, I suppose), which is unlikely to be found on any generic Linux system.
In comparison, here is ldd's output for the old 5.1.0 binary:
Click here to view the secret text
× linux-vdso.so.1 (0x00007f13041d3000)
libSDL-1.2.so.0 => /home/kikuchiyo/drod-tss/Bin/linux-x86_64/libSDL-1.2.so.0 (0x00007f130413e000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f130411d000)
librt.so.1 => /lib64/librt.so.1 (0x00007f1304118000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f1304113000)
libm.so.6 => /lib64/libm.so.6 (0x00007f130402d000)
libc.so.6 => /lib64/libc.so.6 (0x00007f1303e37000)
/lib64/ld-linux-x86-64.so.2 (0x00007f13041d5000)
Come to think of it, maybe a cleaner solution to this dll dependency problem would be packaging the program as an RPM or DEB package (ideally, both). That way dependencies could be declared and managed cleanly and explicitly.
