public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Mike Mason <mmlnx@us.ibm.com>
To: William Cohen <wcohen@redhat.com>
Cc: SystemTAP <systemtap@sources.redhat.com>
Subject: Re: Fedora 7 based Systemtap LiveCD for i686 machines
Date: Mon, 11 Jun 2007 20:04:00 -0000	[thread overview]
Message-ID: <466DAAC1.7050709@us.ibm.com> (raw)
In-Reply-To: <466DA610.5020705@redhat.com>

William Cohen wrote:
> Mike Mason wrote:

[snip]

>>>
>>> The source is already in the debuginfo rpm. However, I don't know 
>>> about getting the cscope information in there. It isn't in an rpm. 
>>> Generating the stuff on the fly probably won't work too well either.
>>
>> I don't see any source coming from the debuginfo rpm.  Where is it 
>> located?
> 
> What I said wasn't quite true. The .c and .h files are around. However, 
> the make and script files are not there. Take a look in 
> /usr/src/debug/kernel-2.6.21 (or similar directory).

Oops, I forgot about kernel-debuginfo-common.  That's where the source comes from.  

I actually was able to do a "yum install cscope", then run "cscope -R" on the kernel source and it worked fine.  All that running the live CD on a 512MB laptop.  If there's room, can we add the cscope rpm to the live CD?  We can just build the cscope database on the fly if needed.

Thanks,
Mike

> 
> -Will
> 

      reply	other threads:[~2007-06-11 20:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-06 22:02 William Cohen
2007-06-08 18:53 ` William Cohen
2007-06-10 15:45   ` Frank Ch. Eigler
     [not found] ` <4669D266.6090304@us.ibm.com>
     [not found]   ` <466AB438.40506@redhat.com>
     [not found]     ` <466D9119.6080702@us.ibm.com>
     [not found]       ` <466D99BB.7070502@redhat.com>
2007-06-11 19:09         ` Mike Mason
2007-06-11 19:44           ` William Cohen
2007-06-11 20:04             ` Mike Mason [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=466DAAC1.7050709@us.ibm.com \
    --to=mmlnx@us.ibm.com \
    --cc=systemtap@sources.redhat.com \
    --cc=wcohen@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).