From: "Frank Ch. Eigler" <fche@redhat.com>
To: naresh kamboju <naresh.kernel@gmail.com>
Cc: systemtap@sources.redhat.com, Dave Brolley <brolley@redhat.com>,
David Smith <dsmith@redhat.com>,
Masami Hiramatsu <mhiramat@redhat.com>,
eugen@debian.org
Subject: Re: Integer constant is too large for 'long' type
Date: Tue, 17 Nov 2009 20:02:00 -0000 [thread overview]
Message-ID: <20091117200109.GA12292@redhat.com> (raw)
In-Reply-To: <f5a7b3810911160744v65634971va7479b491e5afc2d@mail.gmail.com>
Hi -
On Mon, Nov 16, 2009 at 09:14:52PM +0530, naresh kamboju wrote:
> [...]
> In the above line, extra_offset datatype is "long long int" but
> ".build_id_offset is "unsigned long" only. [...]
That's because it presumes that the buildid note section will be
located somewhat after .text. In the case of your arm kernel build,
that's not the case.
> However, I have [reverted] this patch and able to resolve the build
> issue on ARM.
That's only the build issue. Does the code *run* though, meaning does
it actually verify the buildid bits at virtual address 0x0-ish on your
arm kernel? I suspect not.
- FChE
next prev parent reply other threads:[~2009-11-17 20:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-05 8:40 naresh kamboju
2009-11-05 8:47 ` Mark Wielaard
2009-11-05 10:42 ` naresh kamboju
2009-11-05 14:56 ` naresh kamboju
2009-11-05 15:25 ` Frank Ch. Eigler
2009-11-05 15:34 ` naresh kamboju
[not found] ` <20091105153606.GC21665@redhat.com>
[not found] ` <f5a7b3810911050748h1d4e82ft4d5af4a5b14d6d49@mail.gmail.com>
2009-11-05 15:54 ` Frank Ch. Eigler
2009-11-05 16:09 ` naresh kamboju
2009-11-16 15:45 ` naresh kamboju
2009-11-16 18:16 ` Eugeniy Meshcheryakov
2009-11-16 18:24 ` Eugeniy Meshcheryakov
2009-11-26 7:04 ` naresh kamboju
2009-11-17 20:02 ` Frank Ch. Eigler [this message]
2009-11-18 14:51 ` naresh kamboju
2009-11-06 12:13 ` Mark Wielaard
2009-11-06 14:36 ` naresh kamboju
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=20091117200109.GA12292@redhat.com \
--to=fche@redhat.com \
--cc=brolley@redhat.com \
--cc=dsmith@redhat.com \
--cc=eugen@debian.org \
--cc=mhiramat@redhat.com \
--cc=naresh.kernel@gmail.com \
--cc=systemtap@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).