[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#456057: marked as done (FTBFS with GCC 4.3: missing #includes)

Your message dated Tue, 18 Mar 2008 00:40:10 +0100
with message-id <20080317234009.GA28091@galadriel.inutil.org>
and subject line Re: FTBFS with GCC 4.3: missing #includes
has caused the Debian Bug report #456057,
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 owner@bugs.debian.org
immediately.)


-- 
456057: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=456057
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: om
Version: 0.2.0-4
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 om_0.2.0-4 on em64t by sbuild/amd64 0.53
...
> if x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I.    -I../common -g -O2 -DNDEBUG -pipe -fmessage-length=139 -fdiagnostics-show-location=every-line -fno-rtti -fno-exceptions -MT NodeTree.o -MD -MP -MF ".deps/NodeTree.Tpo" -c -o NodeTree.o NodeTree.cpp; \
> 	then mv -f ".deps/NodeTree.Tpo" ".deps/NodeTree.Po"; else rm -f ".deps/NodeTree.Tpo"; exit 1; fi
> NodeTree.cpp: In copy constructor 'Om::NodeTree::iterator::iterator(const Om::NodeTree::iterator&)':
> NodeTree.cpp:315: error: 'memcpy' was not declared in this scope
> NodeTree.cpp: In member function 'Om::NodeTree::iterator& Om::NodeTree::iterator::operator=(const Om::NodeTree::iterator&)':
> NodeTree.cpp:329: error: 'memcpy' was not declared in this scope
> make[5]: *** [NodeTree.o] Error 1
> make[5]: Leaving directory `/build/tbm/om-0.2.0/src/engine'
> make[4]: *** [all] Error 2
> make[4]: Leaving directory `/build/tbm/om-0.2.0/src/engine'
> make[3]: *** [all-recursive] Error 1
> make[3]: Leaving directory `/build/tbm/om-0.2.0/src'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory `/build/tbm/om-0.2.0'
> make[1]: *** [all] Error 2

-- 
Martin Michlmayr
http://www.cyrius.com/

--- End Message ---
--- Begin Message --- 
On Wed, Dec 12, 2007 at 08:19:32PM -0700, Martin Michlmayr wrote:
> Package: om
> Version: 0.2.0-4
> 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

om was removed from the archive, closing.

Cheers,
        Moritz

--- End Message ---
Reply to: