Your message dated Wed, 13 Feb 2008 21:02:05 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#455282: fixed in aria2 0.12.1-1
has caused the Debian Bug report #455282,
regarding FTBFS with GCC 4.3: missing #includes
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
455282: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=455282
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: aria2
Version: 0.11.3-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://www.cyrius.com/journal/2007/05/10#gcc-4.3-include
You can reproduce this problem with gcc-snapshot from unstable. Note
that Red Hat, Novell and Ubuntu have done some work getting packages
to build with GCC 4.3 so there might be patches floating around
somewhere. I suggest you talk to your upstream.
> Automatic build of aria2_0.11.3-1 on em64t by sbuild/amd64 0.53
...
> if x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I.. -Wall -I../lib
> -I../intl -I../intl -I/usr/include -I/usr/include -I/usr/include/libxml2
> -I/usr/include -D_FILE_OFFSET_BITS=64 -DLOCALEDIR=\"/usr/share/locale\"
> -DHAVE_CONFIG_H -g -O2 -MT SocketCore.o -MD -MP -MF ".deps/SocketCore.Tpo"
> -c -o SocketCore.o SocketCore.cc; \
> then mv -f ".deps/SocketCore.Tpo" ".deps/SocketCore.Po"; else rm -f
> ".deps/SocketCore.Tpo"; exit 1; fi
> SocketCore.cc: In member function 'void SocketCore::beginListen(int32_t)':
> SocketCore.cc:103: error: 'memset' was not declared in this scope
> SocketCore.cc: In member function 'SocketCore* SocketCore::acceptConnection()
> const':
> SocketCore.cc:122: error: 'memset' was not declared in this scope
> SocketCore.cc: In member function 'void
> SocketCore::getAddrInfo(std::pair<std::basic_string<char,
> std::char_traits<char>, std::allocator<char> >, int>&) const':
> SocketCore.cc:134: error: 'memset' was not declared in this scope
> SocketCore.cc: In member function 'void
> SocketCore::getPeerInfo(std::pair<std::basic_string<char,
> std::char_traits<char>, std::allocator<char> >, int>&) const':
> SocketCore.cc:145: error: 'memset' was not declared in this scope
> SocketCore.cc: In member function 'void SocketCore::establishConnection(const
> std::string&, int32_t)':
> SocketCore.cc:168: error: 'memset' was not declared in this scope
> SocketCore.cc: In member function 'int32_t SocketCore::shiftPeekData(char*,
> int32_t)':
> SocketCore.cc:394: error: 'memcpy' was not declared in this scope
> SocketCore.cc:399: error: 'memcpy' was not declared in this scope
> SocketCore.cc: In member function 'void SocketCore::addPeekData(char*,
> int32_t)':
> SocketCore.cc:413: error: 'memcpy' was not declared in this scope
> SocketCore.cc:418: error: 'memcpy' was not declared in this scope
> SocketCore.cc: In member function 'int32_t SocketCore::gnutlsPeek(char*,
> int32_t)':
> SocketCore.cc:437: error: 'memcpy' was not declared in this scope
> SocketCore.cc:440: error: 'memcpy' was not declared in this scope
> SocketCore.cc: In static member function 'static const char*
> SocketCore::errorMsg(int)':
> SocketCore.cc:531: error: 'strerror' was not declared in this scope
> make[3]: *** [SocketCore.o] Error 1
> make[3]: Leaving directory `/build/tbm/aria2-0.11.3/src'
--
Martin Michlmayr
http://www.cyrius.com/
--- End Message ---
--- Begin Message ---
Source: aria2
Source-Version: 0.12.1-1
We believe that the bug you reported is fixed in the latest version of
aria2, which is due to be installed in the Debian FTP archive:
aria2_0.12.1-1.diff.gz
to pool/main/a/aria2/aria2_0.12.1-1.diff.gz
aria2_0.12.1-1.dsc
to pool/main/a/aria2/aria2_0.12.1-1.dsc
aria2_0.12.1-1_i386.deb
to pool/main/a/aria2/aria2_0.12.1-1_i386.deb
aria2_0.12.1.orig.tar.gz
to pool/main/a/aria2/aria2_0.12.1.orig.tar.gz
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.
Patrick Ruckstuhl <[EMAIL PROTECTED]> (supplier of updated aria2 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: Tue, 12 Feb 2008 18:33:31 +0100
Source: aria2
Binary: aria2
Architecture: source i386
Version: 0.12.1-1
Distribution: unstable
Urgency: low
Maintainer: Patrick Ruckstuhl <[EMAIL PROTECTED]>
Changed-By: Patrick Ruckstuhl <[EMAIL PROTECTED]>
Description:
aria2 - High speed download utility
Closes: 455282 462762
Changes:
aria2 (0.12.1-1) unstable; urgency=low
.
* New upstream release (Closes: #455282, #462762)
Files:
97e0dad8d4fdd6539b7a4c7bcde6348b 687 net optional aria2_0.12.1-1.dsc
da857c15785a86efbe1149fa2a4d2b0a 1048880 net optional aria2_0.12.1.orig.tar.gz
b15d8c68fa45cf604ec6e9ddb3800ee3 17417 net optional aria2_0.12.1-1.diff.gz
2fb53b59140e2eacc50651cac24c186e 771030 net optional aria2_0.12.1-1_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHs02s+C5cwEsrK54RAmSaAKCLEkIEie27q6sap3SlU/QFvzvnNwCaAqm/
SGy9j37XZzKqTLpPtZSH56Y=
=/i6G
-----END PGP SIGNATURE-----
--- End Message ---
