public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "Keshavamurthy, Anil S" <anil.s.keshavamurthy@intel.com>
To: "Guang Lei Li" <liguangl@cn.ibm.com>
Cc: <systemtap@sources.redhat.com>
Subject: RE: Systemtap scripts unable to compile on RHEL4 U2
Date: Tue, 27 Sep 2005 18:18:00 -0000	[thread overview]
Message-ID: <44BDAFB888F59F408FAE3CC35AB470410222591E@orsmsx409> (raw)


Please see my comments below.

-Anil

>systemtap-owner@sources.redhat.com wrote on 2005-09-27 05:30:48:
>
>> Hi,
>>    I did a full install of the latest and greatest RHEL4
>> U2(2.6.9-20.ELsmp) 
>> on x86_64 box. Trying to compile a simple tap script and 
>seeing errors.
>> 
>> Parsed 'do_fork' -> func 'do_fork'
>> Semantic error: no match for probe point
>>    while: resolving probe point kernel.function("do_fork");
>> Pass 2: analysis failed. Try again ......
>> 
>> 
>> Am I missing anything here? Does this have any dependencies on
>> kernel-debuginfo RPM?
>> Also I did not find kernel-debuginfo RPM on RHEL4 U2 Beta CD's.
>> 
>
>You need kernel-debuginfo RPM.
>
>You can download the kernel src RPM package from 
>rhn.redhat.com, and then:
>  1. install the rpm package
>  2. build the rpm src package:  #cd /usr/src/redhat; rpmbuild -ba 
>SPECS/kernel-2.6.spec --target=x86_64
>    to save your time, you can edit 
>/usr/src/redhat/SPECS/kernel-2.6.spec 
>to comment one or more of the following defines:
>                #define buildup 0
>                #define buildsmp 1
>                #define buildsource 0
>                #define buildhugemem 0
>                #define builddoc 0
>                #define kabi 1
>   finally, rpmbuild will generate kernel-debuginfo, kernel, 
>kernel-devel 
>RPMs in /usr/src/redhat/RPMS/x86_64
>

The above procedure is okay for the developers, but not advisable for
end users I think.
If Systemtap RPM is installed then all its dependencies should be met
else I think there is some 
bug and people get confused.



             reply	other threads:[~2005-09-27 18:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-27 18:18 Keshavamurthy, Anil S [this message]
2005-09-27 19:15 ` William Cohen
2005-09-28  1:00   ` Vara Prasad
  -- strict thread matches above, loose matches on Subject: below --
2005-09-28 11:05 Frank Ch. Eigler
2005-09-26 22:59 Keshavamurthy, Anil S
2005-09-26 21:30 Keshavamurthy, Anil S
2005-09-26 22:23 ` Frank Ch. Eigler
2005-09-27  1:31 ` Guang Lei Li

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=44BDAFB888F59F408FAE3CC35AB470410222591E@orsmsx409 \
    --to=anil.s.keshavamurthy@intel.com \
    --cc=liguangl@cn.ibm.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).