From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <binutils-return-72376-listarch-binutils=sources.redhat.com@sourceware.org>
Received: (qmail 10781 invoked by alias); 13 Jul 2011 00:06:06 -0000
Received: (qmail 10769 invoked by uid 22791); 13 Jul 2011 00:06:05 -0000
X-SWARE-Spam-Status: No, hits=-1.4 required=5.0	tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
Received: from omta01-pub.suddenlink.net (HELO omta01.suddenlink.net) (208.180.40.73)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 13 Jul 2011 00:05:32 +0000
Received: from YOUR1F7593437D ([173.218.216.167]) by omta01.suddenlink.net          (InterMail vM.7.09.02.04 201-2219-117-106-20090629) with ESMTP          id <20110713000532.DYPW22118.omta01.suddenlink.net@YOUR1F7593437D>          for <binutils@sourceware.org>; Tue, 12 Jul 2011 19:05:32 -0500
Message-ID: <001a01cc40f0$95e62b40$a7d8daad@YOUR1F7593437D>
From: "Bill Cunningham" <billcun@suddenlink.net>
To: <binutils@sourceware.org>
References: <000301cc40e7$914a4b10$a7d8daad@YOUR1F7593437D><mcry603jc1z.fsf@coign.corp.google.com><000a01cc40ef$0feacfb0$a7d8daad@YOUR1F7593437D> <mcrtyarjbea.fsf@coign.corp.google.com>
Subject: Re: Where's bfd.h
Date: Wed, 13 Jul 2011 14:32:00 -0000
MIME-Version: 1.0
Content-Type: text/plain;	format=flowed;	charset="iso-8859-1";	reply-type=original
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact binutils-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <binutils.sourceware.org>
List-Subscribe: <mailto:binutils-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/binutils/>
List-Post: <mailto:binutils@sourceware.org>
List-Help: <mailto:binutils-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: binutils-owner@sourceware.org
X-SW-Source: 2011-07/txt/msg00127.txt.bz2

Ian Lance Taylor wrote:
> "Bill Cunningham" <billcun@suddenlink.net> writes:
> 
>> In the compiled compiled binutils-2.21 I get syscat.h ansidecl.h and
>> bfd.h and the libbfd.a static library in the /lib directory. ELF's
>> section struct has a referrence to SH_INFO. This is I believe where a
>> vendor puts information about his ELF file. COFF maybe different.
> 
> The sh_info field of an ELF section header has a different meaning for
> different section types (sh_type field).  It does not have a
> vendor-specific meaning, except, of course, when using a
> vendor-specific section type.
> 
> Vendor specific information is normally put in a vendor specific note
> section (type SHT_NOTE).

    Oh Ok SHT_NOTE. I stand corrected.

Bill