From: Mark Wielaard <mjw@redhat.com>
To: naresh kamboju <naresh.kernel@gmail.com>
Cc: systemtap@sources.redhat.com, "Frank Ch. Eigler" <fche@redhat.com>
Subject: Re: Integer constant is too large for 'long' type
Date: Thu, 05 Nov 2009 08:47:00 -0000 [thread overview]
Message-ID: <1257410818.2529.6.camel@hermans.wildebeest.org> (raw)
In-Reply-To: <f5a7b3810911050040w573c404ft619d6ebb53edd267@mail.gmail.com>
Hi Naresh,
On Thu, 2009-11-05 at 14:10 +0530, naresh kamboju wrote:
> # stap -a arm -B CROSS_COMPILE=/usr/local/arm/cross/devel/bin/arm-dev-
> -p4 -r 2.6.29.4-kzm-arm11-g8de6eff -m five five.stp -vv
> SystemTap translator/driver (version 1.0/0.137 non-git sources)
0.137 is a pretty old version of elfutils, you might want to upgrade to
something newer.
> In file included from /tmp/stapBF1Ti1/five.c:754:
> /tmp/stapBF1Ti1/stap-symbols.h:66980: error: integer constant is too
> large for 'long' type
> /tmp/stapBF1Ti1/stap-symbols.h:66980: error: large integer implicitly
> truncated to unsigned type
Could you build with stap -k, which keeps the temporary file, and post
what code is around stap-symbols.h:66980?
Thanks,
Mark
next prev parent reply other threads:[~2009-11-05 8:47 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 [this message]
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
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=1257410818.2529.6.camel@hermans.wildebeest.org \
--to=mjw@redhat.com \
--cc=fche@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).