Source: onscripter
Version: 0.0.20091011-1
Severity: serious
User: [email protected]
Usertags: qa-ftbfs-20091117 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> g++  -O3 -Wall -fomit-frame-pointer -pipe -c -I/usr/include/SDL 
> -D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/smpeg -I/usr/include/SDL 
> -D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/lua5.1 -I/usr/include/avifile-0.7 
>  -DLINUX -DUSE_LUA -DUSE_AVIFILE -DUSE_OGG_VORBIS -DENABLE_1BYTE_CHAR 
> -DFORCE_1BYTE_CHAR AVIWrapper.cpp
> AVIWrapper.cpp: In member function 'void AVIWrapper::audioCallback(void*, 
> Uint8*, int)':
> AVIWrapper.cpp:169: error: no matching function for call to 
> 'avm::IReadStream::ReadFrames(char*&, int&, int&, uint_t&, uint_t&)'
> /usr/include/avifile-0.7/avifile.h:182: note: candidates are: virtual int 
> avm::IReadStream::ReadFrames(void*, size_t, size_t, size_t&, size_t&)
> AVIWrapper.cpp:170: warning: comparison between signed and unsigned integer 
> expressions
> AVIWrapper.cpp:176: warning: comparison between signed and unsigned integer 
> expressions
> /usr/include/avifile-0.7/avm_output.h: At global scope:
> /usr/include/avifile-0.7/avm_output.h:60: warning: 'avm::AvmOutput* 
> avm::AvmOutput()' defined but not used
> make[1]: *** [AVIWrapper.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2009/11/17/onscripter_0.0.20091011-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