linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
Cc: Yuri Kozlov <yuray-YPGtXv8QU+00kPtPmH8OGQ@public.gmane.org>,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: elf.5: EI_BRAND is not exist in Linux
Date: Sat, 19 Jun 2010 14:49:44 +0200	[thread overview]
Message-ID: <AANLkTikGiluL6-yrgERQ1vZvbXNJvR3uEBPhed4T_thE@mail.gmail.com> (raw)
In-Reply-To: <201002030204.36675.vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>

Hi Yuri, Mike,

On Wed, Feb 3, 2010 at 9:04 AM, Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org> wrote:
> On Wednesday 03 February 2010 01:08:03 Michael Kerrisk wrote:
>> On Thu, Jan 7, 2010 at 11:30 AM, Yuri Kozlov wrote:
>> > From elf.5:
>> >  e_ident     This array of bytes specifies to interpret the file, ...
>> >    EI_BRAND    Start of architecture identification.
>> >
>> > Value for EI_BRAND is not defined in the linux/elf.h (and gabi too).
>> > Maybe add some comment, that is for *BSD only?
>>
>> You've done a patch or two to the elf.5 page in the past. Are you able
>> to comment on the below? I confirmed Yuri's statement: EI_BRAND isn't
>> in glibc 2.11 source.
>
> not being the glibc source isnt terribly important imo (since there are a lot
> of things glibc's elf.h doesnt define), but the fact it isnt in the gabi as
> Yuri notes seems pretty important:
> http://www.sco.com/developers/gabi/latest/ch4.eheader.html
>
> whether it be marked as non-standard (and then we research what random OSes
> actually define it) or simply drop it, either makes sense to me.  the latter
> is obviously less work :).
> -mike

Okay -- I simply removed the test, as shown in the patch below. Okay?

Cheers,

Michael

--- a/man5/elf.5
+++ b/man5/elf.5
@@ -347,9 +347,12 @@ The value for
 .B EI_PAD
 will change in
 the future if currently unused bytes are given meanings.
-.TP
-.BR EI_BRAND
-Start of architecture identification.
+.\" As reported by Yuri Kozlov  and confirmed by Mike Frysinger, EI_BRAND is
+.\" not in GABI (http://www.sco.com/developers/gabi/latest/ch4.eheader.html)
+.\" It looks to be a BSDism
+.\" .TP
+.\" .BR EI_BRAND
+.\" Start of architecture identification.
 .TP
 .BR EI_NIDENT
 The size of the
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2010-06-19 12:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-07 10:30 elf.5: EI_BRAND is not exist in Linux Yuri Kozlov
     [not found] ` <20100107133046.7d380dcb-CpVCSV+zb/Ftei/ch0jEm2ZHpeb/A1Y/@public.gmane.org>
2010-02-03  6:08   ` Michael Kerrisk
     [not found]     ` <cfd18e0f1002022208j7e78def6ycee31e0c818b9351-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-02-03  7:04       ` Mike Frysinger
     [not found]         ` <201002030204.36675.vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2010-06-19 12:49           ` Michael Kerrisk [this message]

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=AANLkTikGiluL6-yrgERQ1vZvbXNJvR3uEBPhed4T_thE@mail.gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org \
    --cc=yuray-YPGtXv8QU+00kPtPmH8OGQ@public.gmane.org \
    /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 NNTP newsgroup(s).