Your message dated Sun, 06 Apr 2008 01:02:44 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#456044: fixed in synaptic 0.61+nmu1
has caused the Debian Bug report #456044,
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.)
--
456044: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=456044
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: synaptic
Version: 0.61
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 synaptic_0.61 on em64t by sbuild/amd64 0.53
...
> rgdebinstallprogress.cc:370: warning: deprecated conversion from string
> constant to 'char*'
> rgdebinstallprogress.cc: In member function 'virtual void
> RGDebInstallProgress::prepare(RPackageLister*)':
> rgdebinstallprogress.cc:680: warning: deprecated conversion from string
> constant to 'gchar*'
> mv -f .deps/rgdebinstallprogress.Tpo .deps/rgdebinstallprogress.Po
> g++ -DHAVE_CONFIG_H -I. -I.. -I../common -I../pixmaps
> -DPACKAGE_DATA_DIR=\""/usr/share"\"
> -DPACKAGE_LOCALE_DIR=\""/usr/share/locale"\"
> -DSYNAPTIC_GLADEDIR=\""/usr/share/synaptic/glade/"\"
> -DSYNAPTIC_PIXMAPDIR=\""/usr/share/synaptic/pixmaps/"\" -DPNG_NO_MMX_CODE
> -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0
> -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0
> -I/usr/lib/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/libpng12
> -I/usr/include/libglade-2.0 -I/usr/include/libxml2 -DPNG_NO_MMX_CODE
> -I/usr/include/freetype2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
> -I/usr/include/gtk-2.0 -I/usr/include/pango-1.0 -I/usr/lib/gtk-2.0/include
> -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/libpng12 -g
> -O2 -MT rgterminstallprogress.o -MD -MP -MF .deps/rgterminstallprogress.Tpo
> -c -o rgterminstallprogress.o rgterminstallprogress.cc
> rgterminstallprogress.cc: In member function 'virtual void
> RGTermInstallProgress::finishUpdate()':
> rgterminstallprogress.cc:158: error: 'strlen' was not declared in this scope
> rgterminstallprogress.cc: In member function 'virtual
> pkgPackageManager::OrderResult
> RGTermInstallProgress::start(pkgPackageManager*, int, int)':
> rgterminstallprogress.cc:220: error: 'exit' was not declared in this scope
> rgterminstallprogress.cc:228: error: 'memset' was not declared in this scope
> make[4]: *** [rgterminstallprogress.o] Error 1
> make[4]: Leaving directory `/build/tbm/synaptic-0.61/gtk'
> make[3]: *** [all-recursive] Error 1
> make[3]: Leaving directory `/build/tbm/synaptic-0.61/gtk'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory `/build/tbm/synaptic-0.61'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/build/tbm/synaptic-0.61'
--
Martin Michlmayr
http://www.cyrius.com/
--- End Message ---
--- Begin Message ---
Source: synaptic
Source-Version: 0.61+nmu1
We believe that the bug you reported is fixed in the latest version of
synaptic, which is due to be installed in the Debian FTP archive:
synaptic_0.61+nmu1.dsc
to pool/main/s/synaptic/synaptic_0.61+nmu1.dsc
synaptic_0.61+nmu1.tar.gz
to pool/main/s/synaptic/synaptic_0.61+nmu1.tar.gz
synaptic_0.61+nmu1_i386.deb
to pool/main/s/synaptic/synaptic_0.61+nmu1_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.
James Vega <[EMAIL PROTECTED]> (supplier of updated synaptic 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: Sat, 05 Apr 2008 18:58:52 -0400
Source: synaptic
Binary: synaptic
Architecture: source i386
Version: 0.61+nmu1
Distribution: unstable
Urgency: low
Maintainer: Michael Vogt <[EMAIL PROTECTED]>
Changed-By: James Vega <[EMAIL PROTECTED]>
Description:
synaptic - Graphical package manager
Closes: 456044
Changes:
synaptic (0.61+nmu1) unstable; urgency=low
.
* Non-maintainer upload.
* Fix FTBFS with gcc-4.3. Thanks to Cyril Brulebois for the patch. (Closes:
#456044)
* Lintian cleanups:
- Correct the format of the NEWS file.
- Use su-to-root instead of gksu for the desktop file.
- Remove the empty /usr/bin directory from synaptic.dirs.
- Do not ignore errors from make clean.
- Use Vcs-Bzr instead of XS-Vcs-Bzr.
Files:
78ffc4113dc4a2538ef5ea8b15e82fac 768 admin optional synaptic_0.61+nmu1.dsc
c9481cb2bf45a728f5d54a28d2716aa0 3441865 admin optional
synaptic_0.61+nmu1.tar.gz
eb225b434814e6cb08f29831740307b6 2134734 admin optional
synaptic_0.61+nmu1_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iEYEARECAAYFAkf4G+kACgkQDb3UpmEybUCrdwCZASVRAV+VFeZIDOFWfSRDQEV/
fuwAn2IqKTpneZ+0cHgk319RLiSSh9QJ
=9ZEa
-----END PGP SIGNATURE-----
--- End Message ---
