@nabijaczleweli I don't know about other systems, but on Solaris, Sun originally shipped Solaris 2.0 without a ranlib command, and later added a shell script that only had "exit 0" to deal with complaints about breaking builds of libraries that still called it.
behold post 015. where da lib runnin, which analyses the perennial "when was the last time a system needed a separate ranlib step?" question (alongside, unfortunately, more UNIX lineage than anyone should care for) https://nabijaczleweli.xyz/content/blogn_t/015-ranlib.html
@nabijaczleweli Yeah having a noop ranlib command (like a symlink to /bin/true) is probably a good enough way to keep compatibility, but it's also just backwards compat for code that's very historic if not possibly broken, like if it would expect a file update like GNU binutils and LLVM do.
@lanodan i mean, by definition, unless you're using ar -S (and let's be real, you aren't), you can have RANLIB=true (effectively like SunOS) and you're not losing anything; so that sounds mighty complicated to do instead of /ranlib/d and /RANLIB/d
and if you /are/ somehow using ar -S, then just run ar -s after instead of ranlib