Source: ruby-tioga
Version: 1.14-1
Severity: serious
Tags: wheezy sid
User: [email protected]
Usertags: qa-ftbfs-20120605 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»/ext/Tioga/FigureMaker'
> compiling __shared_axes.c
> compiling __shared_pdfpath.c
> compiling __shared_pdfcolor.c
> compiling wrappers.c
> compiling __shared_texout.c
> compiling __shared_pdfimage.c
> compiling __shared_makers.c
> compiling __shared_pdf_font_dicts.c
> compiling init.c
> compiling generic.c
> generic.c: In function 'ID_Name':
> generic.c:98:39: warning: return discards 'const' qualifier from pointer 
> target type [enabled by default]
> generic.c: In function 'RAISE_ERROR':
> generic.c:118:1: error: format not a string literal and no format arguments 
> [-Werror=format-security]
> In file included from ../../Dobjects/Dvector/include/dvector.h:27:0,
>                  from generic.c:24:
> generic.c: At top level:
> ../../includes/symbols.h:11:14: warning: 'rb_export_symbol' declared 'static' 
> but never defined [-Wunused-function]
> ../../includes/symbols.h:13:16: warning: 'rb_import_symbol' declared 'static' 
> but never defined [-Wunused-function]
> ../../includes/symbols.h:14:16: warning: 'rb_import_symbol_no_raise' declared 
> 'static' but never defined [-Wunused-function]
> cc1: some warnings being treated as errors
> make[1]: *** [generic.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/06/05/ruby-tioga_1.14-1_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