[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#730890: ovito: FTBFS: Invalid rcc parameters



Source: ovito
Version: 0.9.5-2
Severity: serious
Tags: jessie sid
User: debian-qa@lists.debian.org
Usertags: qa-ftbfs-20131128 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[4]: Entering directory `/«PKGBUILDDIR»/obj-x86_64-linux-gnu'
> /usr/bin/cmake -E cmake_progress_report /«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles 29
> [ 68%] Compiling resource file(s) 
> cd /«PKGBUILDDIR»/src/atomviz && /usr/lib/x86_64-linux-gnu/qt4/bin/rcc -binary -o /«PKGBUILDDIR»/obj-x86_64-linux-gnu/lib/ovito/plugins/atomviz.rcc
> Qt resource compiler
> Usage: /usr/lib/x86_64-linux-gnu/qt4/bin/rcc  [options] <inputs>
> 
> Options:
>   -o file              write output to file rather than stdout
>   -name name           create an external initialization function with name
>   -threshold level     threshold to consider compressing files
>   -compress level      compress input files by level
>   -root path           prefix resource access path with root path
>   -no-compress         disable all compression
>   -binary              output a binary file for use as a dynamic resource
>   -namespace           turn off namespace macros
>   -project             Output a resource file containing all
>                        files from the current directory
>   -version             display version
>   -help                display this information
> make[4]: *** [lib/ovito/plugins/atomviz.rcc] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/11/28/ovito_0.9.5-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.


Reply to: