Your message dated Fri, 28 Mar 2008 07:32:02 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#417786: fixed in yafray 0.0.9+dfsg-1
has caused the Debian Bug report #417786,
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.)
--
417786: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=417786
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: yafray
Version: 0.0.9-2
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 (20070326-1 or higher)
from unstable. (Currently not available for i386, but for amd64, powerpc
and ia64. I hope to have i386 binaries in the archive in ~3 weeks.)
> Automatic build of yafray_0.0.9-2 on coconut0 by sbuild/ia64 0.49
..
> src/yafraycore/vector3d.h: In function 'yafray::PFLOAT
> yafray::ourRandom(int&)':
> src/yafraycore/vector3d.h:291: warning: integer overflow in expression
> g++ -o src/yafraycore/EXR_io.os -c -Wall -DHAVE_CONFIG_H -D_PTHREADS -O3
> -ffast-math -fomit-frame-pointer -fPIC -Isrc/yafraycore -I.
> -I/usr/include/OpenEXR src/yafraycore/EXR_io.cc
> In file included from src/yafraycore/EXR_io.h:5,
> from src/yafraycore/EXR_io.cc:15:
> src/yafraycore/buffer.h: In constructor 'yafray::gBuf_t<T1, T2>::gBuf_t(int,
> int)':
> src/yafraycore/buffer.h:46: error: there are no arguments to 'exit' that
> depend on a template parameter, so a declaration of 'exit' must be available
> src/yafraycore/buffer.h:46: error: (if you use '-fpermissive', G++ will
> accept your code, but allowing the use of an undeclared name is deprecated)
> src/yafraycore/buffer.h: In member function 'void yafray::gBuf_t<T1,
> T2>::set(int, int)':
> src/yafraycore/buffer.h:62: error: there are no arguments to 'exit' that
> depend on a template parameter, so a declaration of 'exit' must be available
> src/yafraycore/buffer.h: In constructor 'yafray::Buffer_t<T>::Buffer_t(int,
> int)':
> src/yafraycore/buffer.h:156: error: there are no arguments to 'exit' that
> depend on a template parameter, so a declaration of 'exit' must be available
> src/yafraycore/buffer.h: In member function 'void
> yafray::Buffer_t<T>::set(int, int)':
> src/yafraycore/buffer.h:178: error: there are no arguments to 'exit' that
> depend on a template parameter, so a declaration of 'exit' must be available
> src/yafraycore/buffer.h: In constructor 'yafray::gBuf_t<T1, T2>::gBuf_t(int,
> int) [with T1 = float, unsigned char T2 = 4u]':
> src/yafraycore/EXR_io.h:18: instantiated from here
> src/yafraycore/buffer.h:46: error: 'exit' was not declared in this scope
> src/yafraycore/buffer.h: In constructor 'yafray::gBuf_t<T1, T2>::gBuf_t(int,
> int) [with T1 = float, unsigned char T2 = 1u]':
> src/yafraycore/EXR_io.h:22: instantiated from here
> src/yafraycore/buffer.h:46: error: 'exit' was not declared in this scope
--- src/yafraycore/buffer.h~ 2007-04-04 14:50:40.000000000 +0000
+++ src/yafraycore/buffer.h 2007-04-04 14:50:45.000000000 +0000
@@ -28,6 +28,7 @@
#endif
#include <cstdio>
+#include <cstdlib>
#include <iostream>
#include "color.h"
--- src/yafraycore/ccthreads.cc~ 2007-04-04 14:51:26.000000000 +0000
+++ src/yafraycore/ccthreads.cc 2007-04-04 14:51:33.000000000 +0000
@@ -1,4 +1,5 @@
#include"ccthreads.h"
+#include<cstdlib>
#include<iostream>
using namespace std;
--- src/yafraycore/renderblock.cc~ 2007-04-04 14:52:38.000000000 +0000
+++ src/yafraycore/renderblock.cc 2007-04-04 14:52:44.000000000 +0000
@@ -1,5 +1,6 @@
#include "renderblock.h"
+#include <cstdlib>
using namespace std;
--
Martin Michlmayr
http://www.cyrius.com/
--- End Message ---
--- Begin Message ---
Source: yafray
Source-Version: 0.0.9+dfsg-1
We believe that the bug you reported is fixed in the latest version of
yafray, which is due to be installed in the Debian FTP archive:
yafray_0.0.9+dfsg-1.diff.gz
to pool/main/y/yafray/yafray_0.0.9+dfsg-1.diff.gz
yafray_0.0.9+dfsg-1.dsc
to pool/main/y/yafray/yafray_0.0.9+dfsg-1.dsc
yafray_0.0.9+dfsg-1_i386.deb
to pool/main/y/yafray/yafray_0.0.9+dfsg-1_i386.deb
yafray_0.0.9+dfsg.orig.tar.gz
to pool/main/y/yafray/yafray_0.0.9+dfsg.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.
Cyril Brulebois <[EMAIL PROTECTED]> (supplier of updated yafray 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, 26 Mar 2008 09:48:50 +0100
Source: yafray
Binary: yafray
Architecture: source i386
Version: 0.0.9+dfsg-1
Distribution: unstable
Urgency: low
Maintainer: Nick Rusnov <[EMAIL PROTECTED]>
Changed-By: Cyril Brulebois <[EMAIL PROTECTED]>
Description:
yafray - a modern, xml-speaking raytracing-based rendering system
Closes: 417786
Changes:
yafray (0.0.9+dfsg-1) unstable; urgency=low
.
* Repack to get rid of the debian/ directory shipped by upstream.
* Add 30_gcc4.3_missing_includes.dpatch to add the missing includes,
which fixes FTBFS with gcc 4.3 (Closes: #417786).
* Move the homepage from the description to the source stanza.
* Move the definition of debhelper compatibility from debian/rules to
debian/compat. Bump it from 4 to 5 (no change needed).
* Bump Standards-Version to 3.7.3 (no change needed).
* Add Vcs-Git and Vcs-Browser now that the packaging is hosted on
alioth.
* Add a watch file.
* Nuke trailing whitespaces in all debian/* files except changelog.
* Move the autotools-dev code snippet from the clean target to the build
one, and delete files in the clean target, through dh_clean. Now
config.guess and config.sub are kept out of the Debian diff.
* Drop the version from the Build-Depends on scons since there's a
sufficient version even in oldstable.
* Adapt the name of the overrides for both shared objects still living
under /usr/lib.
* Refresh GNU/kFreeBSD patch to support version 7 kernels:
+ 10_gnukfreebsd_support.dpatch.
* Document that "-s fork" isn't implemented, in the help message of the
yafray binary. Add a patch for that:
+ 40_document_unimplemented_option.dpatch.
* Adapt the manpage (debian/yafray.sgml) accordingly.
* Move from the SGML format to the POD one for the manpage:
- Replace debian/yafray.sgml with debian/yafray.pod.
- Adjust the manpage generation call to use “pod2man” instead of
“docbook-to-man”.
- Remove docbook-to-man from the Build-Depends.
* Unversion the Suggests: on Blender, since even stable has a sufficient
version.
Files:
cb2b0b94b1f56dde2efb58ca413be006 858 graphics optional yafray_0.0.9+dfsg-1.dsc
179907ec553e67e120d5c044fcd61c56 309857 graphics optional
yafray_0.0.9+dfsg.orig.tar.gz
edbca36510cac0c519a79b2e1079d04d 8246 graphics optional
yafray_0.0.9+dfsg-1.diff.gz
f814e89849c1ed13174e278c394bd87d 618646 graphics optional
yafray_0.0.9+dfsg-1_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFH7JsUVNQJTPEhm4QRAoQuAJ0U7tXhlCkLeC00/8zPfvpmJEoS1gCeLC5E
hXH95Y1zMagoCWm89h/PtCc=
=kfUv
-----END PGP SIGNATURE-----
--- End Message ---
