All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Grundler <iod00d@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: q-tools-0.0 released
Date: Fri, 06 Feb 2004 05:05:21 +0000	[thread overview]
Message-ID: <20040206050521.GA4669@cup.hp.com> (raw)
In-Reply-To: <20040205215009.GA2316@cup.hp.com>

On Thu, Feb 05, 2004 at 02:57:22PM -0800, Stephane Eranian wrote:
> You need to have libpfm-3.0 installed on your system.
> I think Al Stone published the package on the Debian sites.
> You need the development + runtime packages.

Stephane,
Yes, he did.
Debian currently has:
ii  libpfm         2.0-6          IA-64 Performance Monitor (PMU) -- runt-time
ii  libpfm-dev     2.0-6          IA-64 Performance Monitor (PMU) -- developme
ii  pfmon          3.0-2          a performance monitoring tool for Linux/ia64

The pfmon from debian was probably built against "2.0-6" libpfm.
Is that bad?
I'll try this pfmon under 2.6 and see how that works.

> If you don't find the Debian package, then download:
> 
> 	ftp://ftp.hpl.hp.com/pub/linux-ia64/libpfm-3.0.tar.gz


"make install" default is "DESTDIR=/usr/local".
If I rebuild the pfmon package, it's unlikely to find that by default.

> Note that q-tools/libpfm-3.0/pfmon-3.0 ONLY work on 2.6 kernels.

yup - that's what I'm using here.

BTW, Once this is resolved,  someone will need to update the "README"
for q-tools or create a debian package for q-tools.

thanks,
grant

  parent reply	other threads:[~2004-02-06  5:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-05 21:50 q-tools-0.0 released Grant Grundler
2004-02-05 22:28 ` Grant Grundler
2004-02-05 22:57 ` Stephane Eranian
2004-02-06  5:05 ` Grant Grundler [this message]
2004-02-06  7:26 ` Stephane Eranian
2004-02-06 12:24 ` Matthew Wilcox
2004-02-06 17:54 ` Al Stone
  -- strict thread matches above, loose matches on Subject: below --
2003-12-07  1:17 David Mosberger

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=20040206050521.GA4669@cup.hp.com \
    --to=iod00d@hp.com \
    --cc=linux-ia64@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.