Source: imageshack-uploader
Version: 2.2+hg20100408.d802dea89428-4
Severity: serious
Tags: wheezy sid
User: [email protected]
Usertags: qa-ftbfs-20120508 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> g++ -c -m64 -pipe -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector 
> --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -Wall -W 
> -D_REENTRANT 
> -DUNIX_TRANSLATIONS_DIR=\"/usr/share/imageshack-uploader/translations\" 
> -DVERSION=\"2.3.0\" 
> -DDEVELOPER_KEY=\"139ACLMVba0ed423487bdf82ee74c68020d4b198\" -DQT_NO_DEBUG 
> -DQT_XML_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED 
> -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore 
> -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtGui 
> -I/usr/include/qt4/QtXml -I/usr/include/qt4 -Iqtsingleapplication 
> -Iqtsingleapplication -I. -I. -o qtlocalpeer.o 
> qtsingleapplication/qtlocalpeer.cpp
> qtsingleapplication/qtlocalpeer.cpp: In constructor 
> 'QtLocalPeer::QtLocalPeer(QObject*, const QString&)':
> qtsingleapplication/qtlocalpeer.cpp:103:54: error: '::getuid' has not been 
> declared
> qtsingleapplication/qtlocalpeer.cpp:103:54: note: suggested alternative:
> In file included from qtsingleapplication/qtlockedfile_unix.cpp:49:0,
>                  from qtsingleapplication/qtlocalpeer.cpp:67:
> /usr/include/unistd.h:694:16: note:   'QtLP_Private::getuid'
> make[1]: *** [qtlocalpeer.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/05/08/imageshack-uploader_2.2+hg20100408.d802dea89428-4_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 about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.



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

Reply via email to