From: Steven Rostedt <rostedt@goodmis.org>
To: Ross Burton <ross.burton@intel.com>
Cc: linux-kernel@vger.kernel.org, Laura Abbott <labbott@redhat.com>
Subject: Re: [PATCH] scripts/recordmcount: improve EM_METAG define checks
Date: Tue, 26 Jul 2016 17:22:22 -0400 [thread overview]
Message-ID: <20160726172222.093c45d1@gandalf.local.home> (raw)
In-Reply-To: <1468417066-13566-1-git-send-email-ross.burton@intel.com>
On Wed, 13 Jul 2016 14:37:46 +0100
Ross Burton <ross.burton@intel.com> wrote:
> Current glibc (as of c10f90, soon to be 2.24) has an elf.h which defines
> EM_METAG but doesn't also define R_METAG_ADDR32 and _NONE. This results in
> recordmcount not defining any of the META symbols, and the compile failing.
>
> Handle this by checking each #define individually instead of assuming the
> presence.
>
> Signed-off-by: Ross Burton <ross.burton@intel.com>
Actually, Laura beat you to it:
http://lkml.kernel.org/r/1468005530-14757-1-git-send-email-labbott@redhat.com
I'll be applying her patch. I'll also mark it as stable, as it's come
up a few times on IRC as well.
I'll still add a Reported-by from you.
Thanks!
-- Steve
> ---
> scripts/recordmcount.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/scripts/recordmcount.c b/scripts/recordmcount.c
> index e1675927..44ce050 100644
> --- a/scripts/recordmcount.c
> +++ b/scripts/recordmcount.c
> @@ -33,10 +33,14 @@
> #include <string.h>
> #include <unistd.h>
>
> -#ifndef EM_METAG
> /* Remove this when these make it to the standard system elf.h. */
> +#ifndef EM_METAG
> #define EM_METAG 174
> +#endif
> +#ifndef R_METAG_ADDR32
> #define R_METAG_ADDR32 2
> +#endif
> +#ifndef R_METAG_NONE
> #define R_METAG_NONE 3
> #endif
>
next prev parent reply other threads:[~2016-07-26 21:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 13:37 Ross Burton
2016-07-26 21:22 ` Steven Rostedt [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-07-11 19:51 Ross Burton
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=20160726172222.093c45d1@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ross.burton@intel.com \
/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
all inboxes | Powered by JetHome®