@Maijestro
Quote:
This is worth a try, but does not explain why there are no problems here on my machine with the same build.
Same scummvm executable, but maybe different shared objects (*.so) installed on your machine used by it.
Unfortunately most AmigaOS 4.x developers still don't understand at all how shared objects work on AmigaOS 4.x.
1. Although it's supported by ramlib/elf.library PROGDIR:Sobjs must
never be used for shared objects.
2. All .sos have to be installed in the SOBJS: assign (SYS:Sobjs) instead, and there only have to be regular files in it,
never any soft links. If you'd use soft links there you'd get the same .so/.dll hell as on Linux and Windows...
3. OTOH soft links
have to be used in the SDK:libs (GCC:lib, etc.) directories for building executables. Just like for the runtime linker (elf.library) it can only work correctly for the executable linker (GCC:ld, vbcc:vlink, etc.) if the -soname was set correctly when building the shared object.
4. All .sos have to be build with a proper -soname, without it it can't work, and it has to include any dependencies:
For example when building a shared object for clib4 instead of the default AmigaOS 4.x newlib C library the .soname
has to include something like ".clib4" or "_clib4" in it's file- and -sonames, to make sure the incompatible newlib and clib4 shared objects can't be mixed.
As an user there isn't much you can do, with one exception:
If there is a problem with a shared object (.so) use "readelf libfoobar.so" (maybe additional arguments are required) and if there is no "SONAME" section in it it's broken and has to be fixed.