From: naresh kamboju <naresh.kernel@gmail.com>
To: Mark Wielaard <mjw@redhat.com>
Cc: systemtap@sources.redhat.com, "Frank Ch. Eigler" <fche@redhat.com>
Subject: Re: Integer constant is too large for 'long' type
Date: Fri, 06 Nov 2009 14:36:00 -0000 [thread overview]
Message-ID: <f5a7b3810911060635p1b77e5e8k8afc7f67748fb604@mail.gmail.com> (raw)
In-Reply-To: <1257509595.3345.29.camel@springer.wildebeest.org>
Hi Mark,
On Fri, Nov 6, 2009 at 5:43 PM, Mark Wielaard <mjw@redhat.com> wrote:
> On Thu, 2009-11-05 at 16:12 +0530, naresh kamboju wrote:
>> >> 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.
>>
>> yes. it is older version.
>> i have selected this version because in the previous discussion links
>> they have over come few of errors by using elfutils 0.137 version as
>> per the below link
>>
>> http://sourceware.org/bugzilla/show_bug.cgi?id=9738
>>
>> however. suggest me the best compatible version of elfutils with SystemTap-1.0 .
>
> I quickly looked at that bug, I think that isn't related to the problem
> you are seeing (with current systemtap/elfutils it fails differently).
> In general the latest elfutils release (currently 0.143) is preferred
> (later versions are also required for some of the newer features of
> systemtap).
I have build latest systemtap/elfutils
SystemTap translator/driver (version 1.0/0.143 non-git sources)
found following example build issues.
Error:
In file included from /tmp/stap45yApj/five.c:754:
/tmp/stap45yApj/stap-symbols.h:67606: error: integer constant is too
large for 'long' type
/tmp/stap45yApj/stap-symbols.h:67606: error: large integer implicitly
truncated to unsigned type.
discussed same issue with Frank,
I think you have gone through following discussion.
http://sourceware.org/ml/systemtap/2009-q4/msg00418.html
http://sourceware.org/ml/systemtap/2009-q4/msg00419.html
http://sourceware.org/ml/systemtap/2009-q4/msg00420.html
http://sourceware.org/ml/systemtap/2009-q4/msg00436.html
http://sourceware.org/ml/systemtap/2009-q4/msg00437.html
http://sourceware.org/ml/systemtap/2009-q4/msg00438.html
http://sourceware.org/ml/systemtap/2009-q4/msg00439.html
http://sourceware.org/ml/systemtap/2009-q4/msg00441.html
if you have any inputs regarding this issues please provide.
Best regards,
Naresh Kamboju
>
> Cheers,
>
> Mark
>
>
prev parent reply other threads:[~2009-11-06 14:36 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
2009-11-18 14:51 ` naresh kamboju
2009-11-06 12:13 ` Mark Wielaard
2009-11-06 14:36 ` naresh kamboju [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=f5a7b3810911060635p1b77e5e8k8afc7f67748fb604@mail.gmail.com \
--to=naresh.kernel@gmail.com \
--cc=fche@redhat.com \
--cc=mjw@redhat.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).