Source: spice
Version: 0.12.3-0nocelt1
Severity: serious
Tags: jessie sid
User: [email protected]
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Maybe you need to add explicitly the offending lib to LD flags.

Relevant part:
> gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../../common 
> -I../../server -I../../server/tests -I ../../spice-common/ -I 
> ../../spice-common/spice-protocol/      -D_FORTIFY_SOURCE=2  -pthread -lm 
> -lrt  -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat 
> -Werror=format-security -c -o test_playback.o test_playback.c
> /bin/bash ../../libtool  --tag=CC   --mode=link gcc -std=gnu99  -g -O2 
> -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security  
> -Wl,-z,relro -o test_playback basic_event_loop.o  test_playback.o  
> ../../spice-common/common/libspice-common.la ../../server/libspice-server.la  
> libtool: link: gcc -std=gnu99 -g -O2 -fstack-protector 
> --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wl,-z -Wl,relro 
> -o .libs/test_playback basic_event_loop.o test_playback.o  
> ../../spice-common/common/.libs/libspice-common.a 
> ../../server/.libs/libspice-server.so -pthread
> /usr/bin/ld: test_playback.o: undefined reference to symbol 'sin@@GLIBC_2.2.5'
> /lib/x86_64-linux-gnu/libm.so.6: error adding symbols: DSO missing from 
> command line
> collect2: error: ld returned 1 exit status

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/20/spice_0.12.3-0nocelt1_unstable.log

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 EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.


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

Reply via email to