BaSzErr - blog:2016:01:07

ar_vs._cmake

anonymous@undisclosed.example.com (Anonymous) — Tue, 15 Jun 2021 20:09:19 +0000

2016-01-07 - ar vs. cmake

some time ago i've came across an interesting “feature” of ar¹⁾ – it does not store full paths to object files internally. instead it just keeps its name. most of the time this is not a problem. however, if you happen to have more files than command line can fit, creating archive need to be split into multiple calls: creating a libraries and then adding objects groups (multiple times, if needed). cmake does that by default. now if you happen to have object files, named the same, but stored in different directories, and try to add such objects to a static library with ar, you'll end up overwriting old object file, stored inside the archive, with a new file, that just happened to have the same name.

effect? linking error! it's extremely user fiendly²⁾ as you can clearly see your objects are being added to the archive, yet linker says implementation, stored there is missing!

the only way i could think of, to overcome this coincidence of 3 random facts/rules/limitations, is to create helper libraries, that are small enough, to be linked into a single libraries, and then add these libraries as a dependency to “final” library, so that users will not need to be aware of this implementation detail.

btw: if you think 32k is a lot, consider how long nested, auto-generated paths inside build directories, can be! it may not take that many files to trigger such behavior… but took over an hour to find. IT – every day something new! ;)

¹⁾

tool for creating static libraries on linux

²⁾

it's not a typo! ;)

networking_inside_docker

anonymous@undisclosed.example.com (Anonymous) — Tue, 15 Jun 2021 20:09:19 +0000

2016-01-07 - networking inside docker

since some time docker containers have whitelist of capabilities – i.e. they are not allowed to do certain things, unless explicitly stated. common case you can ran into is settings up networking inside a container – say a firewall. there are a lot of weird advices, including running insecure containers! the answer to this is however very simple – just add a proper capability, when starting your container:

docker run --cap-add=NET_ADMIN blabala...

and you're done!

reviewer_s_finger

anonymous@undisclosed.example.com (Anonymous) — Tue, 15 Jun 2021 20:09:19 +0000

2016-01-07 - reviewer's finger

familiar with tennis elbow contusion? i bet that if you do enough code reviews you can get “reviewer's finger” – a hurting finger, that just did far too many kilometers, while scrolling code during reviews. day after day. IT is a dangerous game, after all…