Your message dated Thu, 17 Feb 2005 07:48:12 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#295675: fixed in libtnt 1.2.5-2
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; 8 Nov 2004 15:32:16 +0000
>From [EMAIL PROTECTED] Mon Nov 08 07:32:16 2004
Return-path: <[EMAIL PROTECTED]>
Received: from c203201.adsl.hansenet.de (localhost.localdomain) 
[213.39.203.201] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1CRBVA-00072M-00; Mon, 08 Nov 2004 07:32:16 -0800
Received: from aj by localhost.localdomain with local (Exim 4.34)
        id 1CRBXR-00015W-6Z; Mon, 08 Nov 2004 16:34:37 +0100
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
From: Andreas Jochens <[EMAIL PROTECTED]>
Subject: liblip: FTBFS with gcc-3.4: `data' undeclared
Message-Id: <[EMAIL PROTECTED]>
Date: Mon, 08 Nov 2004 16:34:37 +0100
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
        (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_2004_03_25
X-Spam-Level: 

Package: liblip
Severity: normal
Tags: patch

When building 'liblip' with gcc-3.4 I get the following error:

g++ -DHAVE_CONFIG_H -I. -I. -I.. -Wno-deprecated -c forest.cpp -MT forest.lo 
-MD -MP -MF .deps/forest.TPlo  -fPIC -DPIC -o .libs/forest.lo
In file included from ../tnt/tnt_array1d.h:33,
                 from ../tnt/tnt.h:41,
                 from forest.h:86,
                 from interpol.h:93,
                 from forest.cpp:48:
../tnt/tnt_i_refvec.h: In member function `int TNT::i_refvec<T>::is_null() 
const':
../tnt/tnt_i_refvec.h:204: error: `data' undeclared (first use this function)
../tnt/tnt_i_refvec.h:204: error: (Each undeclared identifier is reported only 
once for each function it appears in.)
make[2]: *** [forest.lo] Error 1
make[2]: Leaving directory `/liblip-1.2/src'

With the attached patch 'liblip' can be compiled using gcc-3.4.

Regards
Andreas Jochens

diff -urN ../tmp-orig/liblip-1.2/tnt/tnt_i_refvec.h ./tnt/tnt_i_refvec.h
--- ../tmp-orig/liblip-1.2/tnt/tnt_i_refvec.h   2004-08-12 03:07:39.000000000 
+0000
+++ ./tnt/tnt_i_refvec.h        2004-11-08 15:29:20.592695064 +0000
@@ -201,7 +201,7 @@
 template<class T>
 int i_refvec<T>::is_null() const
 {
-       return (data == NULL ? 1 : 0);
+       return (this->data == NULL ? 1 : 0);
 }
 
 /*

---------------------------------------
Received: (at 295675-close) by bugs.debian.org; 17 Feb 2005 12:53:09 +0000
>From [EMAIL PROTECTED] Thu Feb 17 04:53:09 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 1D1l9Z-0004af-00; Thu, 17 Feb 2005 04:53:09 -0800
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
        id 1D1l4m-0001cr-00; Thu, 17 Feb 2005 07:48:12 -0500
From: Anibal Monsalve Salazar <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#295675: fixed in libtnt 1.2.5-2
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Thu, 17 Feb 2005 07:48:12 -0500
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: 

Source: libtnt
Source-Version: 1.2.5-2

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

libtnt-dev_1.2.5-2_all.deb
  to pool/main/libt/libtnt/libtnt-dev_1.2.5-2_all.deb
libtnt_1.2.5-2.diff.gz
  to pool/main/libt/libtnt/libtnt_1.2.5-2.diff.gz
libtnt_1.2.5-2.dsc
  to pool/main/libt/libtnt/libtnt_1.2.5-2.dsc



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.
Anibal Monsalve Salazar <[EMAIL PROTECTED]> (supplier of updated libtnt 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: Thu, 17 Feb 2005 23:16:45 +1100
Source: libtnt
Binary: libtnt-dev
Architecture: source all
Version: 1.2.5-2
Distribution: unstable
Urgency: low
Maintainer: Anibal Monsalve Salazar <[EMAIL PROTECTED]>
Changed-By: Anibal Monsalve Salazar <[EMAIL PROTECTED]>
Description: 
 libtnt-dev - interface for scientific computing in C++
Closes: 295675
Changes: 
 libtnt (1.2.5-2) unstable; urgency=low
 .
   * Fixed "FTBFS with gcc-3.4: 'data' undeclared" (Closes: #295675).
     Patch by Andreas Jochens <[EMAIL PROTECTED]>.
Files: 
 a2fe4d4689242d2441fc0b3c473e4c81 534 math optional libtnt_1.2.5-2.dsc
 43b4ea80db52985ad58a8c60c9ba1044 8585 math optional libtnt_1.2.5-2.diff.gz
 32e3d05f48d666b6321bfae35be3ab09 61952 libdevel optional 
libtnt-dev_1.2.5-2_all.deb

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

iD8DBQFCFI16gY5NIXPNpFURAgS8AKCh0uHpWnFycYaucJhXgdmhLmAvjACg22bP
73cPV8c4jr//rjqe3uOSVGg=
=6Iig
-----END PGP SIGNATURE-----


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

Reply via email to