Source: altos
Version: 1.2.1-2
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 -lcryto LD flag.

Relevant part:
> cc -I.. -I. -I../core -I../drivers -I../micropeak -O0 -g -Wall -o ao_fat_test 
> ao_fat_test.c -lssl
> ao_fat_test.c: In function 'long_test_fs':
> ao_fat_test.c:487:2: warning: format '%llu' expects argument of type 'long 
> long unsigned int', but argument 2 has type 'uint64_t' [-Wformat=]
>   printf ("\n   **** Write IO: read %llu write %llu data sectors %llu\n", 
> total_reads, total_writes, (total_file_size + 511) / 512);
>   ^
> ao_fat_test.c:487:2: warning: format '%llu' expects argument of type 'long 
> long unsigned int', but argument 3 has type 'uint64_t' [-Wformat=]
> ao_fat_test.c:487:2: warning: format '%llu' expects argument of type 'long 
> long unsigned int', but argument 4 has type 'uint64_t' [-Wformat=]
> ao_fat_test.c:520:2: warning: format '%llu' expects argument of type 'long 
> long unsigned int', but argument 2 has type 'uint64_t' [-Wformat=]
>   printf ("\n  **** Read IO: read %llu write %llu\n", total_reads, 
> total_writes);
>   ^
> ao_fat_test.c:520:2: warning: format '%llu' expects argument of type 'long 
> long unsigned int', but argument 3 has type 'uint64_t' [-Wformat=]
> /usr/bin/ld: /tmp/ccyn1Pxk.o: undefined reference to symbol 
> 'MD5_Final@@OPENSSL_1.0.0'
> /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0: 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/altos_1.2.1-2_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