bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug binutils/15798] ar q is NOT a synonym for ar r contrary to its docu


From: nickc at redhat dot com
Subject: [Bug binutils/15798] ar q is NOT a synonym for ar r contrary to its documentation
Date: Fri, 23 Aug 2013 11:29:30 +0000

http://sourceware.org/bugzilla/show_bug.cgi?id=15798

Nick Clifton <nickc at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |nickc at redhat dot com

--- Comment #1 from Nick Clifton <nickc at redhat dot com> ---
Created attachment 7162
  --> http://sourceware.org/bugzilla/attachment.cgi?id=7162&action=edit
Revise description of ar's q command

Hi Mikael,

  The documentation was almost right.  The binutils implementation of "ar q"
does behave like "ar r" under some circumstances, specifically when the "s"
modifier is applied to the command.

  What do you think of this revision to the documentation.  With the patch
applied the description for 'q' becomes:

    _Quick append_; Historically, add the files MEMBER... to the end of
     ARCHIVE, without checking for replacement.

     The modifiers 'a', 'b', and 'i' do _not_ affect this operation; new
     members are always placed at the end of the archive.

     The modifier 'v' makes 'ar' list each file as it is appended.

     Since the point of this operation is speed, implementations of 'ar'
     have 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 GNU 'ar' will rebuild the table
     even with a quick append.

     Note - GNU 'ar' treats the command 'qs' as a synonym for 'r' -
     replacing already existing files in the archive and appending new
     ones at the end.

Cheers
  Nick

-- 
You are receiving this mail because:
You are on the CC list for the bug.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]