We often run into scenarios such as
elfmaster@arcana-laptop:~/amp/shiva/modules/x86_64_patches/dwarf_tests$ ./alpr
./alpr: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.31' not found (required by ./alpr)
./alpr: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.32' not found (required by ./alpr)
./alpr: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by ./alpr)
./alpr: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by ./alpr)
It's good to use the required libraries, but sometimes for testing you want to override this. I want to add a feature to Shiva that, at runtime, will remove the requirements. At runtime the .gnu.version section will be modified to remove the verneed entries and so the dynamic linker won't enforce them.
A nice little side-hack feature.
We often run into scenarios such as
It's good to use the required libraries, but sometimes for testing you want to override this. I want to add a feature to Shiva that, at runtime, will remove the requirements. At runtime the .gnu.version section will be modified to remove the verneed entries and so the dynamic linker won't enforce them.
A nice little side-hack feature.