Source: libzrtpcpp
Version: 1.4.6-1
Severity: serious
Tags: wheezy sid
User: [email protected]
Usertags: qa-ftbfs-20110502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> /bin/bash ../libtool --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I..  
>    -g -O2 -g -O2 -Wall -Wno-long-long -Wno-char-subscripts -D_GNU_SOURCE   -c 
> -o ZrtpQueue.lo ZrtpQueue.cpp
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -g -O2 -g -O2 -Wall 
> -Wno-long-long -Wno-char-subscripts -D_GNU_SOURCE -c ZrtpQueue.cpp  -fPIC 
> -DPIC -o .libs/ZrtpQueue.o
> In file included from /usr/include/ccrtp/queuebase.h:49:0,
>                  from /usr/include/ccrtp/iqueue.h:47,
>                  from /usr/include/ccrtp/ioqueue.h:47,
>                  from /usr/include/ccrtp/cqueue.h:47,
>                  from ./libzrtpcpp/ZrtpQueue.h:21,
>                  from ZrtpQueue.cpp:25:
> /usr/include/ccrtp/sources.h:409:11: error: 'ptrdiff_t' does not name a type
> In file included from /usr/include/ccrtp/ioqueue.h:47:0,
>                  from /usr/include/ccrtp/cqueue.h:47,
>                  from ./libzrtpcpp/ZrtpQueue.h:21,
>                  from ZrtpQueue.cpp:25:
> /usr/include/ccrtp/iqueue.h:897:11: error: 'ptrdiff_t' does not name a type
> make[4]: *** [ZrtpQueue.lo] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2011/05/02/libzrtpcpp_1.4.6-1_lsid64.buildlog

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.  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