Package: cone
Version: 0.74-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 cone_0.74-1 on em64t by sbuild/amd64 0.53
...
>  g++ -DHAVE_CONFIG_H -I. -I.. -I./.. -Wall -g -Wall -O2 -c mail.C -o mail.o 
> >/dev/null 2>&1
> /bin/sh ./libtool --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I.   -I.. 
> -I./..  -Wall   -g -Wall -O2 -c -o addmessage.lo addmessage.C
>  g++ -DHAVE_CONFIG_H -I. -I.. -I./.. -Wall -g -Wall -O2 -c addmessage.C  
> -fPIC -DPIC -o .libs/addmessage.o
> addmessage.C: In member function 'virtual void 
> mail::addMessage::assembleMessageRfc822(size_t&, std::string, size_t, 
> mail::callback&)':
> addmessage.C:66: error: 'strerror' was not declared in this scope
> addmessage.C: In member function 'virtual void 
> mail::addMessage::assembleMultipart(size_t&, std::string, const 
> std::vector<long unsigned int, std::allocator<long unsigned int> >&, 
> std::string, const mail::mimestruct::parameterList&, mail::callback&)':
> addmessage.C:92: error: 'strerror' was not declared in this scope
> make[4]: *** [addmessage.lo] Error 1
> make[4]: Leaving directory `/build/tbm/cone-0.74/libmail'

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



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to