Your message dated Mon, 12 Nov 2007 05:18:13 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#417179: fixed in exmap 0.10-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)
--- Begin Message ---
Package: exmap
Version: 0.10-1
Usertags: ftbfs-gcc-4.3
Tags: patch
Your package fails to build with GCC 4.3. Version 4.3 has not been
released yet but I'm building with a snapshot in order to find errors
and give people an advance warning. In GCC 4.3, the C++ header
dependencies have been cleaned up. The advantage of this is that
programs will compile faster. The downside is that you actually
need to directly #include everything you use (but you really should
do this anyway, otherwise your program won't work with any compiler
other than GCC). Some background of this can be found at
http://gcc.gnu.org/PR28080
You can reproduce this problem with gcc-snapshot from unstable.
> Automatic build of exmap_0.10-1 on coconut0 by sbuild/ia64 0.49
....
> g++ -g -Wall -fPIC -c -o jutil.o jutil.cpp
> In file included from jutil.cpp:1:
> jutil.hpp: In member function 'void jutil::ustream::check_enable()':
> jutil.hpp:38: error: 'getenv' was not declared in this scope
> make[2]: *** [jutil.o] Error 1
--- jutil/jutil.hpp~ 2007-04-01 18:34:23.000000000 +0000
+++ jutil/jutil.hpp 2007-04-01 18:34:29.000000000 +0000
@@ -1,6 +1,7 @@
#ifndef _JUTIL_H
#define _JUTIL_H
+#include <cstdlib>
#include <iostream>
#include <string>
#include <list>
--
Martin Michlmayr
http://www.cyrius.com/
--- End Message ---
--- Begin Message ---
Source: exmap
Source-Version: 0.10-2
We believe that the bug you reported is fixed in the latest version of
exmap, which is due to be installed in the Debian FTP archive:
exmap-modules-source_0.10-2_all.deb
to pool/main/e/exmap/exmap-modules-source_0.10-2_all.deb
exmap_0.10-2.diff.gz
to pool/main/e/exmap/exmap_0.10-2.diff.gz
exmap_0.10-2.dsc
to pool/main/e/exmap/exmap_0.10-2.dsc
exmap_0.10-2_i386.deb
to pool/main/e/exmap/exmap_0.10-2_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.
Samuel Mimram <[EMAIL PROTECTED]> (supplier of updated exmap 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: Sun, 11 Nov 2007 16:45:59 +0000
Source: exmap
Binary: exmap-modules-source exmap
Architecture: source i386 all
Version: 0.10-2
Distribution: unstable
Urgency: low
Maintainer: Samuel Mimram <[EMAIL PROTECTED]>
Changed-By: Samuel Mimram <[EMAIL PROTECTED]>
Description:
exmap - determine how much physical memory and swap is used by individual
exmap-modules-source - determine how much physical memory and swap is used by
individual
Closes: 417179 450826
Changes:
exmap (0.10-2) unstable; urgency=low
.
* Added a dependency in debhelper for exmap-modules-source, closes: #450826.
* Added gcc-4.3.dpatch to be able to build with gcc 4.3, closes: #417179.
Files:
c08ccb7e123a963b76a2d3b09a2c2abe 674 devel optional exmap_0.10-2.dsc
4112e1585ea5bf2c451762e0e100c0b6 3708 devel optional exmap_0.10-2.diff.gz
39c66a3c7e97a2d29c23a1921152b30a 14006 devel optional
exmap-modules-source_0.10-2_all.deb
a58b923787c7bb7cc95840a2e90f25e6 133616 devel optional exmap_0.10-2_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHN26lIae1O4AJae8RAmxqAJ4xxRzygmX+Wv4Fhz7B2XLQaknr8gCbB3v2
uHt+1oqLgEUFhVbAJoWe1fc=
=Le8X
-----END PGP SIGNATURE-----
--- End Message ---
