3 ms·
I have never needed to call `patchelf` for anything. If I saw someone putting `--dynamic-linker` in a call to a C compiler I would assume it's out of scope for
by 01HNNWZ0MV43FF 2y ago
I have never needed to call `patchelf` for anything. If I saw someone putting `--dynamic-linker` in a call to a C compiler I would assume it's out of scope for me.
There's already like 100 tools I need to know for my job, I don't want low-level OS and C stuff to add another 50 or even another 20.
This is a little bit "Whatever the world was like when I was 20 is perfect, everything before that is too old, everything after that is too new", but, I'm definitely just reaching for Docker for this. Unless I'm running a GUI application or something else that's hard to containerize.
- walterbell 2y agoOne-line instant alternative to OS/VM/container install. Either path can be chosen.
- theamk 2y agoYou'll want to carefully re-read the text, it's not one line. Where do you think all those libraries come from? And for anything more complex than "hello world", how did we know which libraries to include? Once you solve those two, your thing will be more lines of code than most Dockerfiles.
- AlotOfReading 2y agoIt's 3 different one-liners that all accomplish the same goal. The binary itself will tell you what libraries are needed, so I don't get your objections here.
- kelnos 2y agoTo be fair, it's not one line: before getting to use that one line, have to build a whole other glibc as well. Which is often not a particularly fun process.
- kelnos 2y agoIt's kinda funny because you sorta fall into the same trap you accuse the GP of. Your "Whatever the world was like when I was 20..." quote kinda boils down to "I am fine with the tools I already know how to use and, and I don't want to learn something new". And then you say... you already have your 100 tools and don't want to learn any others. Same deal, really.