RANLIB(1)

πŸ“¦ version 12.2.0, in nixpkgs unstable

🌸 NAME 🌸

okay so bestie, welcome to RANLIB(1) from the GNU Development Tools crew. ranlib = generate index to archive. That's the whole main character job.

✨ SYNOPSIS ✨

ranlib [--plugin name] [-DhHvVt] archive

πŸ¦‹ DESCRIPTION πŸ¦‹

ranlib generates an index to the contents of an archive and stores it in the archive. The index lists each symbol defined by a member of an archive that is a relocatable object file. Yes, every symbol from every relocatable-object member. It's giving library catalog energy.

You can list this index with nm -s or nm --print-armap.

An archive with such an index speeds up linking to the library and lets routines in the library call each other without regard to their placement in the archive. So yes, lowkey a social network for symbols.

The GNU ranlib program is another form of GNU ar; running ranlib is completely equivalent to executing ar -s. Not similar. Not cousin-adjacent. Completely equivalent. periodt.

πŸ’… OPTIONS πŸ’…

  • -h, -H, --help β€” show usage information for ranlib.
  • -v, -V, --version β€” show the version number of ranlib.
  • -D β€” operate in deterministic mode. The symbol map archive member's header will show zero for the UID, GID, and timestamp. When this option is used, multiple runs will produce identical output files. If binutils was configured with --enable-deterministic-archives, then this mode is on by default. It can be disabled with the -U option, described below. So yes, reproducible output bestie. No random timestamp jumps.
  • -t β€” update the timestamp of the symbol map of an archive.
  • -U β€” do not operate in deterministic mode. This is the inverse of the -D option, above: the archive index will get actual UID, GID, timestamp, and file mode values. If binutils was configured without --enable-deterministic-archives, then this mode is on by default.
  • @file β€” read command-line options from file. The options read are inserted in place of the original @file option. If file does not exist, or cannot be read, then the option will be treated literally, and not removed. Options in file are separated by whitespace. A whitespace character may be included in an option by surrounding the entire option in either single or double quotes. Any character (including a backslash) may be included by prefixing the character to be included with a backslash. The file may itself contain additional @file options; any such options will be processed recursively. Nested @file? She said recursive. We love a self-referential icon.

πŸ”₯ SEE ALSO πŸ”₯

Copyright (c) 1991-2018 Free Software Foundation, Inc.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License".


πŸ’– xoxo, your binutils bestie β€” this page comes from binutils-2.30, dated 2018-01-27, and it's still serving RANLIB(1) realness. πŸŽ€

πŸ“¦ where this page comes from