Package: xmp
Version: 2.5.1-1
Severity: serious
User: [email protected]
Usertags: qa-ftbfs-20090620 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> gcc -c -c -g -Wall -O2 -Wall -finline-functions -DHAVE_CONFIG_H   
> -I../include -I. -DVERSION=\"2.5.1\" -D_REENTRANT -fPIC -DENABLE_PLUGIN 
> `pkg-config --cflags audacious` -o audacious.o audacious.c
> audacious.c: In function 'mseek':
> audacious.c:314: error: 'InputPlugin' has no member named 'output'
> audacious.c: In function 'mod_pause':
> audacious.c:323: error: 'InputPlugin' has no member named 'output'
> audacious.c: In function 'get_time':
> audacious.c:334: error: 'InputPlugin' has no member named 'output'
> audacious.c: In function 'init':
> audacious.c:386: warning: implicit declaration of function 'bmp_cfg_db_open'
> audacious.c:386: warning: assignment makes pointer from integer without a cast
> audacious.c:387: warning: implicit declaration of function 
> 'bmp_cfg_db_get_int'
> audacious.c:397: warning: implicit declaration of function 'bmp_cfg_db_close'
> audacious.c: In function 'config_ok':
> audacious.c:944: warning: assignment makes pointer from integer without a cast
> audacious.c:948: warning: implicit declaration of function 
> 'bmp_cfg_db_set_int'
> make[3]: *** [audacious.o] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2009/06/20/xmp_2.5.1-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