AR(1)
okay bestie, welcome to ar(1) from the GNU Development Tools β¨ β she's long, she's iconic, and she's lowkey the backbone of every library you've ever linked against. grab a lil snack π and let's get into it, because we are keeping every single detail, no cap.
π NAME π
ar β create, modify, and extract from archives. periodt. π
β¨ SYNOPSIS β¨
ar [-X32_64]
[-]p[mod]
[--plugin name]
[--target bfdname]
[--output dirname]
[--record-libdeps libdeps]
[--thin]
[relpos] [count] archive [member...] ar -M [< mri-script]
π DESCRIPTION π
so the GNU ar program creates, modifies, and extracts from archives. and what even is an archive? bestie, it's literally a single file holding a whole collection of other files in a structure, and that structure is what lets you pull the original individual files back out. those individual files have a name btw β they're called members of the archive. π«Ά
the original files' contents, mode (permissions), timestamp, owner, and group are preserved in the archive, and can be restored on extraction. she remembers everything, she's giving notes-app-that-never-forgets energy. π
GNU ar can maintain archives whose members have names of any length. however β and this is the plot twist π β depending on how ar is configured on your system, a limit on member-name length may be imposed for compatibility with archive formats maintained with other tools. if it exists, the limit is often 15 characters (typical of formats related to a.out) or 16 characters (typical of formats related to coff).
ar is considered a binary utility because archives of this sort are most often used as libraries holding commonly needed subroutines. and since libraries often will depend on other libraries, ar can also record the dependencies of a library when the --record-libdeps option is specified. we love a supportive queen who tracks her connections. π
ar creates an index to the symbols defined in relocatable object modules in the archive when you specify the modifier s. once created, this index is updated in the archive whenever ar makes a change to its contents β save for the q update operation, which is the one lil exception π. an archive with such an index speeds up linking to the library, so it's kind of a big deal.
you may use nm -s or nm --print-armap to list this index table. and if an archive lacks the table? another form of ar called ranlib can be used to add just the table. she's got a whole extended universe fr fr. π
GNU ar can optionally create a thin archive, which contains a symbol index and references to the original copies of the member files of the archive. this is useful for building libraries for use within a local build tree, where the relocatable objects are expected to remain available, and copying the contents of each object would only waste time and space. thin archive = main character who refuses to duplicate effort. π
an archive can either be thin or it can be normal. it cannot be both at the same time. and once an archive is created, its format cannot be changed without first deleting it and then creating a new archive in its place. so choose wisely, bestie, because there is no glow-up reversal for this one. π
thin archives are also flattened, so that adding one thin archive to another thin archive does not nest it, the way it would happen with a normal archive. instead, the elements of the first archive are added individually to the second archive. no nesting dolls here, just vibes. π¦
the paths to the elements of the archive are stored relative to the archive itself. π§
GNU ar is designed to be compatible with two different facilities, and honestly? versatile. you can control its activity using command-line options, like the different varieties of ar on Unix systems β or, if you specify the single command-line option -M, you can control it with a script supplied via standard input, like the MRI "librarian" program. β¨
π₯ OPTIONS π₯
GNU ar allows you to mix the operation code p and modifier flags mod in any order, within the first command-line argument. any order!! we love flexibility. π
if you wish, you may begin the first command-line argument with a dash. (optional dash, she's chill like that.)
the p keyletter specifies what operation to execute; it may be any of the following, but you must specify only one of them:
dβ Delete modules from the archive. specify the names of modules to be deleted as member...; the archive is untouched if you specify no files to delete.- if you specify the
vmodifier,arlists each module as it is deleted. π
- if you specify the
mβ use this operation to move members in an archive.- the ordering of members in an archive can make a difference in how programs are linked using the library, if a symbol is defined in more than one member. so like... the lineup actually matters. π
- if no modifiers are used with
"m", any members you name in the member arguments are moved to the end of the archive; you can use thea,b, orimodifiers to move them to a specified place instead.
pβ Print the specified members of the archive, to the standard output file. if thevmodifier is specified, show the member name before copying its contents to standard output.- if you specify no member arguments, all the files in the archive are printed.
qβ Quick append; historically, add the files member... to the end of archive, without checking for replacement.- the modifiers
a,b, andido not affect this operation; new members are always placed at the end of the archive. - the modifier
vmakesarlist each file as it is appended. - since the point of this operation is speed, implementations of
arhave the option of not updating the archive's symbol table if one exists. too many different systems however assume that symbol tables are always up-to-date, so GNUarwill rebuild the table even with a quick append. - Note β GNU
artreats the commandqsas a synonym forrβ replacing already existing files in the archive and appending new ones at the end.
- the modifiers
rβ Insert the files member... into archive (with replacement). this operation differs fromqin that any previously existing members are deleted if their names match those being added. out with the old, in with the new. π«- if one of the files named in member... does not exist,
ardisplays an error message, and leaves undisturbed any existing members of the archive matching that name. - by default, new members are added at the end of the file; but you may use one of the modifiers
a,b, orito request placement relative to some existing member. - the modifier
vused with this operation elicits a line of output for each file inserted, along with one of the lettersaorrto indicate whether the file was appended (no old member deleted) or replaced.
- if one of the files named in member... does not exist,
sβ Add an index to the archive, or update it if it already exists. note this command is an exception to the rule that there can only be one command letter, as it is possible to use it as either a command or a modifier. in either case it does the same thing. she contains multitudes. πtβ Display a table listing the contents of archive, or those of the files listed in member... that are present in the archive. normally only the member name is shown, but if the modifierOis specified, then the corresponding offset of the member is also displayed. finally, in order to see the modes (permissions), timestamp, owner, group, and size, thevmodifier should be included. π§Ύ- if you do not specify a member, all files in the archive are listed.
- if there is more than one file with the same name (say,
fie) in an archive (sayb.a),ar t b.a fielists only the first instance; to see them all, you must ask for a complete listing β in our example,ar t b.a. the way that she only shows you the first one is so sneaky π
xβ Extract members (named member) from the archive. you can use thevmodifier with this operation, to request thatarlist each name as it extracts it.- if you do not specify a member, all files in the archive are extracted.
- > β οΈ files cannot be extracted from a thin archive, and there are restrictions on extracting from archives created with
P: the paths must not be absolute, may not contain"..", and any subdirectories in the paths must exist. if it is desired to avoid these restrictions then used the--outputoption to specify an output directory.
a number of modifiers (mod) may immediately follow the p keyletter, to specify variations on an operation's behavior:
aβ Add new files after an existing member of the archive. if you use the modifiera, the name of an existing archive member must be present as the relpos argument, before the archive specification.bβ Add new files before an existing member of the archive. if you use the modifierb, the name of an existing archive member must be present as the relpos argument, before the archive specification. (same asi).cβ Create the archive. the specified archive is always created if it did not exist, when you request an update. but a warning is issued unless you specify in advance that you expect to create it, by using this modifier. she's like "girl, you didn't tell me we were making a whole new file??" πDβ Operate in deterministic mode. when adding files and the archive index, use zero for UIDs, GIDs, timestamps, and use consistent file modes for all files. when this option is used, ifaris used with identical options and identical input files, multiple runs will create identical output files regardless of the input files' owners, groups, file modes, or modification times. reproducibility, she ate. π₯- if
binutilswas configured with--enable-deterministic-archives, then this mode is on by default. it can be disabled with theUmodifier, below.
- if
fβ Truncate names in the archive. GNUarwill normally permit file names of any length. this will cause it to create archives which are not compatible with the nativearprogram on some systems. if this is a concern, thefmodifier may be used to truncate file names when putting them in the archive.iβ Insert new files before an existing member of the archive. if you use the modifieri, the name of an existing archive member must be present as the relpos argument, before the archive specification. (same asb).lβ Specify dependencies of this library. the dependencies must immediately follow this option character, must use the same syntax as the linker command line, and must be specified within a single argument. i.e., if multiple items are needed, they must be quoted to form a single command line argument. for example:
l "-L/usr/local/lib -lmydep1 -lmydep2"
Nβ Uses the count parameter. this is used if there are multiple entries in the archive with the same name. extract or delete instance count of the given name from the archive. she's counting, bestie. π’oβ Preserve the original dates of members when extracting them. if you do not specify this modifier, files extracted from the archive are stamped with the time of extraction. choose your timeline wisely β³Oβ Display member offsets inside the archive. use together with thetoption.Pβ Use the full path name when matching or storing names in the archive. archives created with full path names are not POSIX compliant, and thus may not work with tools other than up to date GNU tools. modifying such archives with GNUarwithout usingPwill remove the full path names unless the archive is a thin archive. note thatPmay be useful when adding files to a thin archive sincerwithoutPignores the path when choosing which element to replace. Thus
ar rcST archive.a subdir/file1 subdir/file2 file1
β¦means the first subdir/file1 gets replaced by file1 from wherever you're standing right now. Add P and that replacement justβ¦ doesn't happen. Boundaries, bestie. π
sβ writes an object-file index into the archive, or refreshes one you already have, even if literally nothing else about the archive changes. You can run this one alongside any operation, or all by itself, dealer's choice. Runningar son an archive is exactly the same energy as runningranlibon it. Periodt.Sβ do not generate an archive symbol table. This can make building a big library in several steps faster, but it's gonna hurt if the resulting archive gets handed to the linker. To actually get a symbol table, you have to leave off theSmodifier on your lastarrun, or just runranlibon the archive. There's no third option, sorry. πTβ deprecated alias for--thin. Don't use it, fr fr. It's not recommended because in a lot ofarimplementationsTmeans something completely different, as specified by the X/Open System Interface. Chaos behavior. πuβ normallyar r...inserts all the files you list into the archive. If you only want to insert the ones that are newer than existing members with the same names, this is your modifier.uis allowed only for ther(replace) operation. In particular, the comboquis not allowed, because checking timestamps would instantly kill the speed advantage you got fromq. Makes sense, right? Checking is the whole cost. π«Ά
Heads up β if an archive was created in a deterministic manner (say, via theDmodifier), then replacement will always happen and theumodifier does absolutely nothing. It's giving decoration.
Uβ do not operate in deterministic mode. This is the inverse of theDmodifier above: added files and the archive index get their actual UID, GID, timestamp, and file mode values. Raw. Unfiltered. β¨
This is the default unless binutils was configured with --enable-deterministic-archives. So it's the main character unless someone changed the build.
vβ this modifier asks for the verbose version of an operation. Lots of operations show you extra info β filenames processed, that kind of thing β when you tackvon the end. Bestie love a paper trail. πVβ this modifier shows the version number ofar. Just the version. That's the whole job. πΈ
π command-line options that are neither modifiers nor actions π
The ar program also supports some command-line options which are neither modifiers nor actions, but which do change its behaviour in specific ways: (their words, but like⦠accurate)
--helpβ displays the list of command-line options supported byarand then exits. Instant gratification, zero side effects.--versionβ displays the version information ofarand then exits. Same energy, different info. π-X32_64βarignores an initial option spelled-X32_64, for compatibility with AIX. The behaviour produced by this option is the default for GNUar.ardoes not support any of the other-Xoptions; in particular, it does not support-X32, which is the default for AIXar. So it's a vibe check it justβ¦ passes. π¦--plugin nameβ the optional command-line switch--plugin namecausesarto load the plugin called name, which adds support for more file formats, including object files with link-time optimization information.
This option is only available if the toolchain has been built with plugin support enabled. No plugin support, no plugin option. π
If --plugin is not provided, but plugin support has been enabled, then ar iterates over the files in ${libdir}/bfd-plugins in alphabetic order and the first plugin that claims the object in question is used. First come, first served, alphabetically.
Please note that this plugin search directory is not the one used by ld's -plugin option. In order to make ar use the linker plugin it must be copied into the ${libdir}/bfd-plugins directory. For GCC based compilations the linker plugin is called liblto_plugin.so.0.0.0. For Clang based compilations it is called LLVMgold.so. The GCC plugin is always backwards compatible with earlier versions, so it is sufficient to just copy the newest one. Copy the newest one and go. π
--target targetβ the optional command-line switch--target bfdnamespecifies that the archive members are in an object code format different from your system's default format. See--output dirnameβ the--outputoption can be used to specify a path to a directory into which archive members should be extracted. If this option is not specified then the current directory will be used. Home sweet home as the default, cute. π
Note β although the presence of this option does imply axextraction operation, that option must still be included on the command line. You don't getxfor free just because you said where to put stuff.
--record-libdeps libdepsβ the--record-libdepsoption is identical to thelmodifier, just handled in long form. Same thing, longer name, iykyk.--thinβ make the specified archive a thin archive. If it already exists and is a regular archive, the existing members must be present in the same directory as archive. No teleporting members, they gotta be right there next to it. β¨@fileβ read command-line options from file. The options read are inserted in place of the original@fileoption. If file does not exist, or cannot be read, then the option will be treated literally, and not removed. Ghosted, basically. π»
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. It's @files all the way down. π
π SEE ALSO π
nm(1), ranlib(1), and the Info entries for binutils. Go read your siblings, they're iconic too. π
π COPYRIGHT π
Copyright (c) 1991-2026 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".
okay that's the whole page bestie, we made it π«Ά this was binutils-2.47, dated 2026-09-19, and you just read AR(1). go archive something, you're doing amazing. πβ¨
π¦ where this page comes from
- ubuntu stonking: binutils-sh-elf 2.47+3build2 Β· GPL-3.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms