Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 14 Aug 2014 10:07:42 -0700
From:      Marcel Moolenaar <>
To:        Konstantin Belousov <>
Cc:        Marcel Moolenaar <>, Phil Shafer <>, John-Mark Gurney <>, "Simon J. Gerraty" <>,, Poul-Henning Kamp <>
Subject:   Re: XML Output: libxo - provide single API to output TXT, XML, JSON and HTML
Message-ID:  <>
In-Reply-To: <>
References:  <> <> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help

Content-Transfer-Encoding: 7bit
Content-Type: text/plain;

On Aug 14, 2014, at 1:52 AM, Konstantin Belousov <> wrote:

> On Thu, Aug 14, The ELF spec says:
>>    Note Section
>>    Sometimes a vendor or system builder needs to mark an object
>>    file with special information that other programs will check
>>    for conformance, compatibility, etc. Sections of type SHT_NOTE
>>    and program header elements of type PT_NOTE can be used for
>>    this purpose. The note information in sections and program
>>    header elements holds any number of entries, each of which is
>>    an array of 4-byte words in the format of the target processor.
>>    Labels appear below to help explain note information organization,
>>    but they are not part of the specification.
> ELF standard scope is about build toolchain and C runtime, where the
> cited paragraph makes perfect sense.

That's a self-imposed precondition that is not
present in the spec. You're just as liberal in
the interpretation as Phil is. You just on the
other side of the argument.

I am definitely interested in what you think a
system builder is given your objection.

Marcel Moolenaar

Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
Content-Type: application/pgp-signature;
Content-Description: Message signed with OpenPGP using GPGMail

Comment: GPGTools -



Want to link to this message? Use this URL: <>