public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nitin Gupta <gupta@equator.com>
To: Nitin Gupta <gupta@equator.com>
Cc: binutils@sources.redhat.com
Subject: Re: ar not compatible between 2.11 and 2.13 ?
Date: Thu, 01 May 2003 01:26:00 -0000	[thread overview]
Message-ID: <3EB077D7.70600@equator.com> (raw)
In-Reply-To: <3EB07785.9030904@equator.com>

>
>> OBSERVATION:
>> I noticed that if the object name is 13 alphabets long
>> say
>> ABCDEFGHIJKLM.o
>>
>> and I build an archive using 2.13 ar by
>> ar rucv libXYZ.a ABCDEFGHIJKLM.o
>> than
>>
>> ar t libXYZ.a (using 2.11 ar) yields
>> ABCDEFGHIJKLM.
>>
>> Nick Clifton wrote:
>>
>>>Hi Nitin,
>>>
>>>  
>>>
>>>>I noticed that if I create an archive on machine using ar version
>>>>2.13 (2.13.90.0.2 to be precise) say libXYZ.a, if I do a "ar t" on
>>>>machine using 2.11 (2.11.90.0.8), I see
>>>>
>>>>ar t libXYZ.a
>>>>X.
>>>>Y.o
>>>>Z.o
>>>>
>>>>It is just an example.  The problem, is that the object names are
>>>>missing ".o" when I do an "ar t" on a archive created using 2.13
>>>>version. BTW, it shows it correct if I use same version of archive
>>>>to see the contents.
>>>>
>>>>Please let me know, if that is never suppose to work, or if there is
>>>>a patch for it.
>>>>    
>>>>
>>>
>>>There are no more patches available or planned to be produced for
>>>version 2.11 of binutils.  Since the 2.13 version is working correctly
>>>I recommend sticking with that version.
>>>
>>>Cheers
>>>        Nick
>>>
>>>
>>>  
>>>
>

-- 
-NI+IN



  parent reply	other threads:[~2003-05-01  1:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-29 19:41 Nitin Gupta
2003-04-29 19:46 ` Nitin Gupta
2003-04-30  8:34   ` Nick Clifton
     [not found]     ` <3EB076C6.8070106@equator.com>
     [not found]       ` <3EB07785.9030904@equator.com>
2003-05-01  1:26         ` Nitin Gupta [this message]
2003-05-05  5:40     ` H. J. Lu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3EB077D7.70600@equator.com \
    --to=gupta@equator.com \
    --cc=binutils@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).