Explore >> Select a destination
|
You are here 
|
blog.atsign.dev | ||
| | | | |
boricj.net
|
|
| | | | | In this series of articles, we will study a program written in C that prints the ASCII table on its standard output. This particular program will: use the Executable and Linkable Format for its binary artifacts; target the 32-bit, little endian MIPS III instruction set architecture; run on the Linux operating system. | |
| | | | |
staex.io
|
|
| | | | | IoT devices sometimes have too little resources to pull and run heavyweight Docker images. In this article we show how to reduce the size by 36-91% using patchelf and strace tools without recompiling containerized applications. | |
| | | | |
nguyenhuythanh.com
|
|
| | | | | I think everyone who uses NixOS should have encountered this dreaded error (I'm using a "random" binary file that comes from Codeium, which is an code completion extension powered by AI): ./language_server_linux_x64 # zsh: no such file or directory: ./language_server_linux_x64 It is quite elusive on why does this happen. After taking a while searching and reading, I "sort of" understood the problem, but can only put it to my terms like this: in other OSes (Ubuntu for example), C libraries can be found using a global PATH, while NixOS does not have the same semantic; it leads to the problem that compiled binaries cannot find the C libraries they need. | |
| | | | |
xeiaso.net
|
|
| | | Xe Iaso's personal website. | ||
