Your message dated Mon, 18 May 2009 19:29:29 +0300
with message-id <20090518162929.ga3...@rama>
and subject line Re: Bug#529263: FTBFS with GCC 4.4: missing #include
has caused the Debian Bug report #529272,
regarding FTBFS with GCC 4.4: missing #include
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.)
--
529272: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=529272
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mozzemberek
Version: 0.1.1-3
User: [email protected]
Usertags: ftbfs-gcc-4.4
Your package fails to build with GCC 4.4, which has cleaned up some more
C++ headers. You always have to #include headers directly and cannot
rely for things to be included indirectly.
You can reproduce this problem with gcc-4.4/g++-4.4 from unstable.
I guess you know about this too?
> Automatic build of mozzemberek_0.1.1-3 on em64t by sbuild/amd64 0.53
...
> g++ -g -O2 -g -Wall -O2 -Wall -Wno-non-virtual-dtor -fno-rtti -fno-exceptions
> -fshort-wchar -fPIC -c -I/usr/include/nspr
> -I/usr/lib/xulrunner-devel-1.9/sdk/include
> -I/usr/lib/xulrunner-devel-1.9/include -I/usr/include/xulrunner-1.9/xpcom
> -I/usr/include/xulrunner-1.9/spellchecker -I/usr/include/xulrunner-1.9/uconv
> -I/usr/include/xulrunner-1.9/unicharutil -I/usr/include/xulrunner-1.9/xulapp
> -I/usr/include/xulrunner-1.9/unstable -include mozilla-config.h -include
> xpcom-config.h -o zsconn.o zsconn.cpp
> zsconn.cpp: In constructor 'ZSConn::ZSConn()':
> zsconn.cpp:30: warning: deprecated conversion from string constant to 'char*'
> zsconn.cpp: In member function 'virtual void ZSConn::init()':
> zsconn.cpp:48: error: 'perror' was not declared in this scope
> zsconn.cpp:53: error: 'perror' was not declared in this scope
> zsconn.cpp:63: error: 'perror' was not declared in this scope
> zsconn.cpp: In member function 'Z_CHECK_RESULT ZSConn::spellCheck(const
> std::string&) const':
> zsconn.cpp:103: error: 'perror' was not declared in this scope
> zsconn.cpp: In member function 'std::vector<std::basic_string<char,
> std::char_traits<char>, std::allocator<char> >,
> std::allocator<std::basic_string<char, std::char_traits<char>,
> std::allocator<char> > > > ZSConn::getSuggestions(const std::string&) const':
> zsconn.cpp:128: error: 'perror' was not declared in this scope
> make[2]: *** [zsconn.o] Error 1
> make[2]: Leaving directory `/build/tbm/mozzemberek-0.1.1/src'
--
Martin Michlmayr
http://www.cyrius.com/
--- End Message ---
--- Begin Message ---
[Rail: you forgot to mention that you fixed #529272 in the changelog of
mozzemberek-0.1.2-2, closing the bug via BTS.]
* Rail Aliev [2009-05-18 14:45:00+0400]
> On Monday 18 May 2009 14:05:37 Martin Michlmayr wrote:
> > Package: zpspell
> > Version: 0.4.2-4
> > User: [email protected]
> > Usertags: ftbfs-gcc-4.4
> > Tags: patch
> >
> > Your package fails to build with GCC 4.4, which has cleaned up some more
> > C++ headers. You always have to #include headers directly and cannot
> > rely for things to be included indirectly.
>
> Martin,
> Thanks a lot for the patch. The upstream version has fixed this bug already.
> To be fixed in the next upload.
>
> Recai,
> Could you pull the changes from bzr.debian.org and reupload this package?
Done (#529263).
* Rail Aliev [2009-05-18 15:39:37+0400]
> On Monday 18 May 2009 15:23:43 Martin Michlmayr wrote:
> > Package: mozzemberek
> > Version: 0.1.1-3
> > User: [email protected]
> > Usertags: ftbfs-gcc-4.4
> >
> > Your package fails to build with GCC 4.4, which has cleaned up some more
> > C++ headers. You always have to #include headers directly and cannot
> > rely for things to be included indirectly.
> >
> > You can reproduce this problem with gcc-4.4/g++-4.4 from unstable.
> >
> > I guess you know about this too?
>
> Yes, already fixed in upstream.
>
> Recai,
> Could you upload a new version?
Done (#529272).
--
roktas
--- End Message ---
