Package: pan
Version: 0.132-2
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20080318 qa-ftbfs
Justification: FTBFS on i386

Hi,

During a rebuild of all packages in sid, your package failed to build on i386.

Relevant part:
> if i486-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I../..  -I../.. 
> -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/gmime-2.0 
> -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include   -pthread 
> -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include     -g -O2 -MT my-tree.o 
> -MD -MP -MF ".deps/my-tree.Tpo" -c -o my-tree.o my-tree.cc; \
>       then mv -f ".deps/my-tree.Tpo" ".deps/my-tree.Po"; else rm -f 
> ".deps/my-tree.Tpo"; exit 1; fi
> my-tree.cc: In member function 'virtual void 
> pan::DataImpl::MyTree::set_filter(pan::Data::ShowType, const 
> pan::FilterInfo*)':
> my-tree.cc:99: error: 'g_assert' was not declared in this scope
> my-tree.cc: In member function 'void 
> pan::DataImpl::MyTree::add_articles(const std::vector<const 
> pan::DataImpl::ArticleNode*, std::allocator<const 
> pan::DataImpl::ArticleNode*> >&)':
> my-tree.cc:404: error: 'g_assert' was not declared in this scope
> my-tree.cc:417: error: 'g_assert' was not declared in this scope
> my-tree.cc:481: error: 'g_assert' was not declared in this scope
> my-tree.cc:494: error: 'g_assert' was not declared in this scope
> make[4]: *** [my-tree.o] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2008/03/18

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot containing a sid i386
environment.  Internet was not accessible from the build systems.

-- 
| Lucas Nussbaum
| [EMAIL PROTECTED]   http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED]             GPG: 1024D/023B3F4F |



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

Reply via email to