Your message dated Mon, 04 Apr 2005 17:32:03 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#302914: fixed in callgrind 0.9.11-1
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 3 Apr 2005 19:42:12 +0000
>From [EMAIL PROTECTED] Sun Apr 03 12:42:12 2005
Return-path: <[EMAIL PROTECTED]>
Received: from gluck.debian.org [192.25.206.10] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DIAz6-0003zu-00; Sun, 03 Apr 2005 12:42:12 -0700
Received: from mail-out.m-online.net [212.18.0.9] 
        by gluck.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DIAz5-0004cw-00; Sun, 03 Apr 2005 13:42:11 -0600
Received: from mail.m-online.net (svr20.m-online.net [192.168.3.148])
        by mail-out.m-online.net (Postfix) with ESMTP id 61E977CA2;
        Sun,  3 Apr 2005 21:41:38 +0200 (CEST)
Received: from atari.stigge.org (ppp-82-135-5-192.mnet-online.de [82.135.5.192])
        by mail.m-online.net (Postfix) with ESMTP id 1555666949;
        Sun,  3 Apr 2005 21:41:34 +0200 (CEST)
Received: from [192.168.5.99] (localhost [127.0.0.1])
        by atari.stigge.org (Postfix) with ESMTP id 890E1100442A0;
        Sun,  3 Apr 2005 21:41:33 +0200 (CEST)
From: Roland Stigge <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: callgrind: FTBFS: vg_skin.h unreachable
Message-Id: <[EMAIL PROTECTED]>
Date: Sun,  3 Apr 2005 21:41:33 +0200 (CEST)
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Package: callgrind
Version: 0.9.10-1
Severity: serious

Hi,

building the package callgrind in a clean sid build environment
(with pbuilder) on i386 results in:

=========================================================================
[...]
dh_testdir
# Add here commands to configure the package.
./configure --host=i386-linux --build=i386-linux --prefix=/usr 
--mandir=\${prefix}/share/man --infodir=\${prefix}/share/info
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for i386-linux-gcc... i386-linux-gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether i386-linux-gcc accepts -g... yes
checking for i386-linux-gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of i386-linux-gcc... gcc3
checking for i386-linux-g++... i386-linux-g++
checking whether we are using the GNU C++ compiler... yes
checking whether i386-linux-g++ accepts -g... yes
checking dependency style of i386-linux-g++... gcc3
checking for a BSD-compatible install... /usr/bin/install -c
checking for i386-linux-ranlib... no
checking for ranlib... ranlib
checking for valgrind installation... in /usr
checking if vg_skin.h is available... configure: error: No. Needs header files 
from Valgrind (2.0.x/2.2.x).
Perhaps a valgrind-dev package is missing in your installation?
make: *** [config.status] Error 1
=========================================================================

Thanks for considering.


--
DARTS - Debian Archive Regression Test Suite
http://darts.alioth.debian.org/

Please note that this report has not been generated fully automatically.
DARTS just helped finding the problem.

---------------------------------------
Received: (at 302914-close) by bugs.debian.org; 4 Apr 2005 21:43:25 +0000
>From [EMAIL PROTECTED] Mon Apr 04 14:43:25 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DIZLx-0000IW-00; Mon, 04 Apr 2005 14:43:25 -0700
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
        id 1DIZAx-0006OD-00; Mon, 04 Apr 2005 17:32:03 -0400
From: Philipp Frauenfelder <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#302914: fixed in callgrind 0.9.11-1
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Mon, 04 Apr 2005 17:32:03 -0400
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 
X-CrossAssassin-Score: 4

Source: callgrind
Source-Version: 0.9.11-1

We believe that the bug you reported is fixed in the latest version of
callgrind, which is due to be installed in the Debian FTP archive:

callgrind_0.9.11-1.diff.gz
  to pool/main/c/callgrind/callgrind_0.9.11-1.diff.gz
callgrind_0.9.11-1.dsc
  to pool/main/c/callgrind/callgrind_0.9.11-1.dsc
callgrind_0.9.11.orig.tar.gz
  to pool/main/c/callgrind/callgrind_0.9.11.orig.tar.gz
valgrind-callgrind_0.9.11-1_i386.deb
  to pool/main/c/callgrind/valgrind-callgrind_0.9.11-1_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Philipp Frauenfelder <[EMAIL PROTECTED]> (supplier of updated callgrind package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Mon,  4 Apr 2005 23:03:39 +0200
Source: callgrind
Binary: valgrind-callgrind
Architecture: source i386
Version: 0.9.11-1
Distribution: unstable
Urgency: low
Maintainer: Philipp Frauenfelder <[EMAIL PROTECTED]>
Changed-By: Philipp Frauenfelder <[EMAIL PROTECTED]>
Description: 
 valgrind-callgrind - call-graph skin for valgrind
Closes: 284515 299498 301970 302914
Changes: 
 callgrind (0.9.11-1) unstable; urgency=low
 .
   * New upstream release:
     - Support for Valgrind 2.4.0.
     - Fix for handling of function name patterns on command line (exact
       matching, and wildcards now fully supported)
     - Cache-Reuse metrics. Use --cacheuse=yes and metric "SLoss" to locate
       badly aligned/layouted data structures. This shows the wasted amount
       of memory channel bandwidth, as it is the amount of data which was
       loaded into cache but actually never used. Experimental!
      Closes: #302914, #299498, #301970
   *  Changed package description: s/calltree/call-graph/ to prevent
      confusion with the old package name.
      Closes: #284515
Files: 
 7d16018a5552af305bba278ea37b8639 609 devel extra callgrind_0.9.11-1.dsc
 a4c41e6b389a14830191f11a92ed8b91 265674 devel extra 
callgrind_0.9.11.orig.tar.gz
 c4abe93fd32529667bf203032268eb0d 28490 devel extra callgrind_0.9.11-1.diff.gz
 61462c05234e4964969b4bf5e8221ec4 111168 devel extra 
valgrind-callgrind_0.9.11-1_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFCUa4IWLF0MZ2lytgRAlEYAJ48hdVqEC7XLkJcKVn6w1v6nTEj3wCfX3To
5XsNf2Wj6G5+ScTBG/g2PIY=
=/g63
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to