This is the mail archive of the
mailing list for the binutils project.
Re: archive of archives
- From: nick clifton <nickc at redhat dot com>
- To: NightStrike <nightstrike at gmail dot com>
- Cc: Cary Coutant <ccoutant at google dot com>, Binutils <binutils at sourceware dot org>
- Date: Wed, 01 May 2013 11:37:08 +0100
- Subject: Re: archive of archives
- References: <CAF1jjLtCm9Nuua4hytxsvgE1tSnypLUan=R1L6o0BCNjSd437g at mail dot gmail dot com> <CAHACq4qM+2ZziXdncX-VZibHmJ6NArR0fg9yAFy=jFQTN1Z8uw at mail dot gmail dot com> <CAF1jjLv3-9-tvQh0z-=FzjfGFVm4HywFT3DKm19qGA1ZUfWUXQ at mail dot gmail dot com> <CAF1jjLuqcgvWOuo6j_iX_CGjkSZBJJKDwS4prKVX=NH-3e=tQw at mail dot gmail dot com> <517FD619 dot 7020304 at redhat dot com> <CAF1jjLtWNcycW31F3tuUpgvuR81CnpnEraKH3t2gDoK32cTBWw at mail dot gmail dot com>
What I was trying to express in this email was that I found a method
that does in fact work. The MRI script that I mentioned produces a
library that other tools, like nm or dlltool --identify can handle.
And in fact, even ld likes it.
Is it possible that the MRI script that I provided does what you
suggest -- unpacks each library and adds the original objects into the
new library, effectively flattening it?
Yes - exactly that.
See the binutils documentation - specifically the section on "ar scripts".