From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29638 invoked by alias); 29 Jun 2005 05:03:51 -0000 Mailing-List: contact binutils-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sources.redhat.com Received: (qmail 29592 invoked by uid 22791); 29 Jun 2005 05:03:44 -0000 Received: from yosemite.airs.com (HELO yosemite.airs.com) (205.217.158.180) by sourceware.org (qpsmtpd/0.30-dev) with SMTP; Wed, 29 Jun 2005 05:03:44 +0000 Received: (qmail 11083 invoked by uid 10); 29 Jun 2005 05:03:42 -0000 Received: (qmail 19599 invoked by uid 500); 29 Jun 2005 05:02:42 -0000 Mail-Followup-To: binutils@sourceware.org, mkrzyz@interia.pl To: =?utf-8?b?TWFyZWsgS3J6ecW8b3dzaw==?= =?utf-8?b?aQ==?= Cc: binutils@sourceware.org Subject: Re: problem with function bfd_slurp_armap from bfd library References: <42C14C4F.2050106@interia.pl> From: Ian Lance Taylor Date: Wed, 29 Jun 2005 05:03:00 -0000 In-Reply-To: <42C14C4F.2050106@interia.pl> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.4 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-SW-Source: 2005-06/txt/msg00628.txt.bz2 Marek Krzy=C5=BCowski writes: > I have a question to developers of binutils, actually sending toward > these people, who take care about bfd library. Accordance with my > knowledge, function bfd_slurp_armap executes one of the function > relevant to type of map (list of symbols) inserted in static library > (COFF or BSD). Ranlib and ar, as I know, insert string of characters > begins from '/' at the beginning of the static library. It is > information for linker that it will be followed by list of > symbols. Unfortunetely, this is BSD format, but bfd library (function > bfd_slurp_armap) invokes function do_slurp_coff_armap!!! Why ?! The archive map is stored as an entry in the archive, as though it were a file itself. If the name is "__.SYMDEF", it is treated as a BSD style archive map. If the name is simply "/" (which is, incidentally, a name which can never be the name of a file), it is treated as a COFF style archive map. ELF archives are the same as COFF archives. So, from your description, you need to find out why your BSD style archive map was named "/" rather than "__.SYMDEF". Ian