From: Michael Kerrisk <mtk.manpages-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
To: Yuri Kozlov <yuray-YPGtXv8QU+00kPtPmH8OGQ@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
Subject: Re: elf.5: EI_BRAND is not exist in Linux
Date: Wed, 3 Feb 2010 07:08:03 +0100 [thread overview]
Message-ID: <cfd18e0f1002022208j7e78def6ycee31e0c818b9351@mail.gmail.com> (raw)
In-Reply-To: <20100107133046.7d380dcb-CpVCSV+zb/Ftei/ch0jEm2ZHpeb/A1Y/@public.gmane.org>
Hey Mike,
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.
Cheers,
Michael
On Thu, Jan 7, 2010 at 11:30 AM, Yuri Kozlov <yuray-YPGtXv8QU+00kPtPmH8OGQ@public.gmane.org> wrote:
> Hello.
>
> 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?
>
> --
> Best Regards,
> Yuri Kozlov
>
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Author of "The Linux Programming Interface" http://blog.man7.org/
--
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
next prev parent reply other threads:[~2010-02-03 6:08 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 [this message]
[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
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=cfd18e0f1002022208j7e78def6ycee31e0c818b9351@mail.gmail.com \
--to=mtk.manpages-gm/ye1e23mwn+bqq9rbeug@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@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).