Your message dated Wed, 23 Jan 2008 14:02:02 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#462000: fixed in lshw 02.12.01-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: lshw
Version: 02.12.01-1
Usertags: ftbfs-gcc-4.3
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). There's some more information about this at
http://gcc.gnu.org/gcc-4.3/porting_to.html
You can reproduce this problem with gcc-4.3 or gcc-snapshot from
unstable.
> Automatic build of lshw_02.12.01-1 on em64t by sbuild/amd64 0.53
...
> c++ -Wall -g -O2 -DPREFIX=\"/usr\" -DSBINDIR=\"/usr/bin\"
> -DMANDIR=\"/usr/share/man\" -DDATADIR=\"/usr/share\" -c ide.cc -o ide.o
> c++ -Wall -g -O2 -DPREFIX=\"/usr\" -DSBINDIR=\"/usr/bin\"
> -DMANDIR=\"/usr/share/man\" -DDATADIR=\"/usr/share\" -c cdrom.cc -o cdrom.o
> cdrom.cc: In function 'bool scan_cdrom(hwNode&)':
> cdrom.cc:58: error: 'INT_MAX' was not declared in this scope
> make[2]: *** [cdrom.o] Error 1
> make[2]: Leaving directory `/build/tbm/lshw-02.12.01/src/core'
> make[1]: *** [core] Error 2
--
Martin Michlmayr
http://www.cyrius.com/
--- End Message ---
--- Begin Message ---
Source: lshw
Source-Version: 02.12.01-2
We believe that the bug you reported is fixed in the latest version of
lshw, which is due to be installed in the Debian FTP archive:
lshw-gtk_02.12.01-2_i386.deb
to pool/main/l/lshw/lshw-gtk_02.12.01-2_i386.deb
lshw_02.12.01-2.diff.gz
to pool/main/l/lshw/lshw_02.12.01-2.diff.gz
lshw_02.12.01-2.dsc
to pool/main/l/lshw/lshw_02.12.01-2.dsc
lshw_02.12.01-2_i386.deb
to pool/main/l/lshw/lshw_02.12.01-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.
Ghe Rivero <[EMAIL PROTECTED]> (supplier of updated lshw 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: Wed, 23 Jan 2008 14:20:46 +0100
Source: lshw
Binary: lshw lshw-gtk
Architecture: source i386
Version: 02.12.01-2
Distribution: unstable
Urgency: low
Maintainer: Ghe Rivero <[EMAIL PROTECTED]>
Changed-By: Ghe Rivero <[EMAIL PROTECTED]>
Description:
lshw - information about hardware configuration
lshw-gtk - information about hardware configuration
Closes: 462000
Changes:
lshw (02.12.01-2) unstable; urgency=low
.
* More fixes for gcc4.3. Closes: #462000
* Updated Debian-Policy Standards-Version to 3.7.3
Files:
3b66f7e1596d5e556a8c4031ec8f5af2 587 utils optional lshw_02.12.01-2.dsc
c0056eef4a1055a7f8fc2baebb637af6 12450 utils optional lshw_02.12.01-2.diff.gz
11d78f0ec89322875196e4751786bb80 313832 utils optional lshw_02.12.01-2_i386.deb
09d449e27e518c1f2cdcb820549046b8 432362 utils optional
lshw-gtk_02.12.01-2_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHl0bIZttaNibwIPcRAhzSAKDJieXtuba8V3D1r7RFPgRyWsaSDwCg4HTa
IQUItPMvvFnBwewthbC/uqA=
=2xa6
-----END PGP SIGNATURE-----
--- End Message ---
