patchelf VS ruby-vips-lambda

I mean, we don't have to hack the elf loader if we just rewrite every elf binary using patchelf: https://github.com/NixOS/patchelf

The parent commenter is already suggesting "just run a regex", so it seems like a trivial extension to their simple solution to "just run patchelf on every binary on your system"

Patching paths in text files typically used substituteInPlace (including in cowsay). For dynamic libraries, patchelf is typically used.

Install patchelf.

Thank you! I followed the instruction here, but it looks like I didn't actually install it, because my pacman -Q patchelf did not find anything. Maybe I was missing a dependency. Also, it was late so I didn't pay attention to warnings at the time.

How does an article on NixOS talk about the `rpath` issue without also mentioning the `patchelf` utility that NixOS developers created to solve this issue? It's a small tool that lets you modify ELF executables and binaries. It's also the recommended way for NixOS users to modify binaries to work properly.

https://github.com/NixOS/patchelf

So install it? https://github.com/NixOS/patchelf

NixOS doesn't have stable paths to shared libraries like macOS or other linux distributions (and this is the core feature) and always need to patch elf for current paths ( https://github.com/NixOS/patchelf ).

Prior to Lambda Containers we had to build a Lambda Layer using a myriad of techniques. The result was always something in the /opt directory, yet finding the right balance of what to put in that directory has always been a pain. For example, if your gem uses FFI (like ruby-vips) how do I build a layer, test it, and make sure that same layer is available for local development? Often times this required engineering some Docker & AWS SDK coordination. Not a simple process when means it could easily break or slow down testing upgrades to either the gem or supporting layer.