Bug#718072: twitter-bootstrap: FTBFS: ParseError: Unrecognised input in /«BUILDDIR»/twitter-bootstrap-2.0.2+dfsg/less/mixins.less on line 522, column 7

2013-07-28 Thread David Suárez 
Source: twitter-bootstrap
Version: 2.0.2+dfsg-3
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130726 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[2]: Entering directory `/«BUILDDIR»/twitter-bootstrap-2.0.2+dfsg'
> rm -rf bootstrap
> mkdir -p bootstrap/img
> mkdir -p bootstrap/css
> mkdir -p bootstrap/js
> cp img/* bootstrap/img/
> lessc ./less/bootstrap.less > bootstrap/css/bootstrap.css
> ParseError: Unrecognised input in 
> /«BUILDDIR»/twitter-bootstrap-2.0.2+dfsg/less/mixins.less on line 
> 522, column 7:
> 521 .spanX (@index) when (@index > 0) {
> 522   (~".span@{index}") { .span(@index); }
> 523   .spanX(@index - 1);
> 
> make[2]: *** [bootstrap] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/07/26/twitter-bootstrap_2.0.2+dfsg-3_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 debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130728082819.GA6716@Aeris.MIDGAR

Bug#724118: awffull: FTBFS: help2man: can't get `--version' info from /«PKGBUILDDIR»/debian/awffull/usr/sbin/awffull_history_regen

2013-09-22 Thread David Suárez 
Source: awffull
Version: 3.10.2-3
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130922 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[1]: Entering directory `/«PKGBUILDDIR»'
> help2man /«PKGBUILDDIR»/debian/awffull/usr/sbin/awffull_history_regen \
>   -n awffull_history_regen -s 1 \
>   -o /«PKGBUILDDIR»/debian/awffull_history_regen.1
> help2man: can't get `--version' info from 
> /«PKGBUILDDIR»/debian/awffull/usr/sbin/awffull_history_regen
> Try `--no-discard-stderr' if option outputs to stderr
> make[1]: *** [override_dh_installman] Error 2

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/09/22/awffull_3.10.2-3_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 debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130922174304.GA24568@Aeris.MIDGAR

Bug#724177: upse: FTBFS: make[1]: *** No rule to make target `buildsys.mk'. Stop.

2013-09-22 Thread David Suárez 
Source: upse
Version: 1.0.0-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130922 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):
>  fakeroot debian/rules clean
> dh clean 
>dh_testdir
>dh_auto_clean
> make[1]: Entering directory `/«PKGBUILDDIR»'
> Makefile:3: buildsys.mk: No such file or directory
> make[1]: *** No rule to make target `buildsys.mk'.  Stop.
> make[1]: Leaving directory `/«PKGBUILDDIR»'
> dh_auto_clean: make -j1 distclean returned exit code 2
> make: *** [clean] Error 2

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/09/22/upse_1.0.0-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 debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130922192129.GA29608@Aeris.MIDGAR

Bug#724214: mcs: FTBFS: make[1]: *** No rule to make target `buildsys.mk'. Stop.

2013-09-22 Thread David Suárez 
Source: mcs
Version: 0.7.2-3
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130922 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):
>  fakeroot debian/rules clean
> dh clean --with=autotools-dev
>dh_testdir
>dh_auto_clean
> make[1]: Entering directory `/«PKGBUILDDIR»'
> Makefile:4: buildsys.mk: No such file or directory
> make[1]: *** No rule to make target `buildsys.mk'.  Stop.
> make[1]: Leaving directory `/«PKGBUILDDIR»'
> dh_auto_clean: make -j1 distclean returned exit code 2
> make: *** [clean] Error 2

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/09/22/mcs_0.7.2-3_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 debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130922185316.GA27767@Aeris.MIDGAR

Bug#725593: gpointing-device-settings: FTBFS: automake: error: global options already processed

2013-10-06 Thread David Suárez 
Source: gpointing-device-settings
Version: 1.5.1-6
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20131006 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[1]: Entering directory `/«PKGBUILDDIR»'
> autoreconf -f -i
> configure.ac:12: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected 
> in body
> ../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
> ../../lib/autoconf/general.m4:2661: _AC_LINK_IFELSE is expanded from...
> ../../lib/autoconf/general.m4:2678: AC_LINK_IFELSE is expanded from...
> m4/libtool.m4:1022: _LT_SYS_MODULE_PATH_AIX is expanded from...
> m4/libtool.m4:4170: _LT_LINKER_SHLIBS is expanded from...
> m4/libtool.m4:5252: _LT_LANG_C_CONFIG is expanded from...
> m4/libtool.m4:138: _LT_SETUP is expanded from...
> m4/libtool.m4:67: LT_INIT is expanded from...
> m4/libtool.m4:103: AM_PROG_LIBTOOL is expanded from...
> configure.ac:12: the top level
> configure.ac:12: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected 
> in body
> ../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
> ../../lib/autoconf/general.m4:2661: _AC_LINK_IFELSE is expanded from...
> ../../lib/autoconf/general.m4:2678: AC_LINK_IFELSE is expanded from...
> m4/libtool.m4:4170: _LT_LINKER_SHLIBS is expanded from...
> m4/libtool.m4:5252: _LT_LANG_C_CONFIG is expanded from...
> m4/libtool.m4:138: _LT_SETUP is expanded from...
> m4/libtool.m4:67: LT_INIT is expanded from...
> m4/libtool.m4:103: AM_PROG_LIBTOOL is expanded from...
> configure.ac:12: the top level
> configure.ac:12: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected 
> in body
> ../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
> ../../lib/autoconf/general.m4:2661: _AC_LINK_IFELSE is expanded from...
> ../../lib/autoconf/general.m4:2678: AC_LINK_IFELSE is expanded from...
> m4/libtool.m4:1022: _LT_SYS_MODULE_PATH_AIX is expanded from...
> m4/libtool.m4:4170: _LT_LINKER_SHLIBS is expanded from...
> m4/libtool.m4:5252: _LT_LANG_C_CONFIG is expanded from...
> m4/libtool.m4:138: _LT_SETUP is expanded from...
> m4/libtool.m4:67: LT_INIT is expanded from...
> m4/libtool.m4:103: AM_PROG_LIBTOOL is expanded from...
> configure.ac:12: the top level
> configure.ac:12: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected 
> in body
> ../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
> ../../lib/autoconf/general.m4:2661: _AC_LINK_IFELSE is expanded from...
> ../../lib/autoconf/general.m4:2678: AC_LINK_IFELSE is expanded from...
> m4/libtool.m4:4170: _LT_LINKER_SHLIBS is expanded from...
> m4/libtool.m4:5252: _LT_LANG_C_CONFIG is expanded from...
> m4/libtool.m4:138: _LT_SETUP is expanded from...
> m4/libtool.m4:67: LT_INIT is expanded from...
> m4/libtool.m4:103: AM_PROG_LIBTOOL is expanded from...
> configure.ac:12: the top level
> configure.ac:12: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected 
> in body
> ../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
> ../../lib/autoconf/general.m4:2661: _AC_LINK_IFELSE is expanded from...
> ../../lib/autoconf/general.m4:2678: AC_LINK_IFELSE is expanded from...
> m4/libtool.m4:1022: _LT_SYS_MODULE_PATH_AIX is expanded from...
> m4/libtool.m4:4170: _LT_LINKER_SHLIBS is expanded from...
> m4/libtool.m4:5252: _LT_LANG_C_CONFIG is expanded from...
> m4/libtool.m4:138: _LT_SETUP is expanded from...
> m4/libtool.m4:67: LT_INIT is expanded from...
> m4/libtool.m4:103: AM_PROG_LIBTOOL is expanded from...
> configure.ac:12: the top level
> configure.ac:12: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected 
> in body
> ../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
> ../../lib/autoconf/general.m4:2661: _AC_LINK_IFELSE is expanded from...
> ../../lib/autoconf/general.m4:2678: AC_LINK_IFELSE is expanded from...
> m4/libtool.m4:4170: _LT_LINKER_SHLIBS is expanded from...
> m4/libtool.m4:5252: _LT_LANG_C_CONFIG is expanded from...
> m4/libtool.m4:138: _LT_SETUP is expanded from...
> m4/libtool.m4:67: LT_INIT is expanded from...
> m4/libtool.m4:103: AM_PROG_LIBTOOL is expanded from...
> configure.ac:12: the top level
> libtoolize: putting auxiliary files in `.'.
> libtoolize: copying file `./ltmain.sh'
> libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
> libtoolize: copying file `m4/libtool.m4'
> libtoolize: copying file `m4/ltoptions.m4'
> libtoolize: copying file `m4/ltsugar.m4'
> libtoolize: copying file `m4/ltversion.m4'
> libtoolize: copying file `m4/lt~obsolete.m4'
> automake: error: global options already processed
> automake: Please contact .
>  at /usr/share/automake-1.14/Automake/Channels.pm line 662,  line 82.
>   Automake::Channels::msg('automake', '', 'global options already 
> processed') called at /usr/share/automake-1.14/Automake/ChannelDefs.pm line 
> 212
>   Automake::ChannelDefs::prog_error('global options a

Bug#725569: libpam-unix2: FTBFS: configure.in:36: error: required file './compile' not found

2013-10-06 Thread David Suárez 
Source: libpam-unix2
Version: 1:2.6-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20131006 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):
>  debian/rules build
> dh_testdir
> autoreconf -vf
> autoreconf: Entering directory `.'
> autoreconf: configure.in: not running autopoint: --install not given
> autoreconf: running: aclocal --force -I m4
> aclocal: warning: autoconf input should be named 'configure.ac', not 
> 'configure.in'
> autoreconf: configure.in: tracing
> autoreconf: configure.in: not using Libtool
> autoreconf: running: /usr/bin/autoconf --force
> autoreconf: running: /usr/bin/autoheader --force
> autoreconf: running: automake --force-missing
> automake: warning: autoconf input should be named 'configure.ac', not 
> 'configure.in'
> configure.in:97: warning: The 'AM_PROG_MKDIR_P' macro is deprecated, and its 
> use is discouraged.
> configure.in:97: You should use the Autoconf-provided 'AC_PROG_MKDIR_P' macro 
> instead,
> configure.in:97: and use '$(MKDIR_P)' instead of '$(mkdir_p)'in your 
> Makefile.am files.
> configure.in:36: error: required file './compile' not found
> configure.in:36:   'automake --add-missing' can install 'compile'
> automake: warning: autoconf input should be named 'configure.ac', not 
> 'configure.in'
> autoreconf: automake failed with exit status: 1
> make: *** [config.status] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/10/06/libpam-unix2_2.6-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 debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20131006190116.GA5808@Aeris.MIDGAR

Bug#730935: nitpic: FTBFS: b-d on libiberty-dev instead of binutils-dev

2013-11-30 Thread David Suárez 
Source: nitpic
Version: 0.1-14
Severity: serious
Tags: jessie sid
User: debian...@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.

Due to the switch of libiberty to his own package (libiberty|libiberty-dev).

Relevant part (hopefully):
> c++ -o nitpic -g -O2 -fno-strict-aliasing  main.o ic.o info.o instr.o 
> pu_lib.o reg.o sim.o util.o 16c84.o -lXaw  -lXmu -lXt -lSM -lICE -lXext -lX11 
> -lXt -lSM -lICE -lXext -lX11   -Wl,-Bstatic -lbfd -lopcodes -Wl,-Bdynamic -lz 
> -liberty -lm -lc -ldl   
> /usr/bin/ld: cannot find -liberty
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/11/28/nitpic_0.1-14_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 debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20131130153204.GA7034@Aeris.MIDGAR

Bug#730890: ovito: FTBFS: Invalid rcc parameters

2013-11-30 Thread David Suárez 
Source: ovito
Version: 0.9.5-2
Severity: serious
Tags: jessie sid
User: debian...@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] 
> 
> 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
>   -helpdisplay 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.


-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20131130164312.GA9345@Aeris.MIDGAR

Bug#733353: wdm: FTBFS: ld: cannot find -lungif

2013-12-28 Thread David Suárez 
Source: wdm
Version: 1.28-16
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20131226 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 the needed build depend.

Relevant part (hopefully):
> gcc -Wl,-z,relro -Wl,--as-needed -L./bin  -L/usr/lib -L/usr/lib 
> src/TestLogin/TestLogin.o -lWINGs -lWUtil -lwraster -ltiff -lXpm -lpng -ljpeg 
> -lungif -lXft -lXext -lXext -lX11 -lm -lWUtil -lfontconfig -lcrypt -lutil  
> -lwdm -lSM -lICE -lXext -lX11 -lm  -lXinerama -o bin/TestLogin
> /usr/bin/ld: cannot find -lungif
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/12/26/wdm_1.28-16_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 debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20131228190416.GA19528@Aeris.MIDGAR

Bug#738384: python-repoze.what: FTBFS: ImportError: No module named what.authorize

2014-02-09 Thread David Suárez 
Source: python-repoze.what
Version: 1.0.9-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140208 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):
> running install
> running build
> running build_py
> running egg_info
> writing requirements to repoze.what.egg-info/requires.txt
> writing repoze.what.egg-info/PKG-INFO
> writing namespace_packages to repoze.what.egg-info/namespace_packages.txt
> writing top-level names to repoze.what.egg-info/top_level.txt
> writing dependency_links to repoze.what.egg-info/dependency_links.txt
> writing entry points to repoze.what.egg-info/entry_points.txt
> reading manifest file 'repoze.what.egg-info/SOURCES.txt'
> writing manifest file 'repoze.what.egg-info/SOURCES.txt'
> running install_lib
> Skipping installation of 
> /«PKGBUILDDIR»/debian/python-repoze.what/usr/lib/python2.7/site-packages/repoze/__init__.py
>  (namespace package)
> copying repoze/what/release.py -> 
> /«PKGBUILDDIR»/debian/python-repoze.what/usr/lib/python2.7/site-packages/repoze/what
> copying repoze/what/predicates.py -> 
> /«PKGBUILDDIR»/debian/python-repoze.what/usr/lib/python2.7/site-packages/repoze/what
> copying repoze/what/authorize.py -> 
> /«PKGBUILDDIR»/debian/python-repoze.what/usr/lib/python2.7/site-packages/repoze/what
> Skipping installation of 
> /«PKGBUILDDIR»/debian/python-repoze.what/usr/lib/python2.7/site-packages/repoze/what/__init__.py
>  (namespace package)
> copying repoze/what/middleware.py -> 
> /«PKGBUILDDIR»/debian/python-repoze.what/usr/lib/python2.7/site-packages/repoze/what
> copying repoze/what/adapters/testutil.py -> 
> /«PKGBUILDDIR»/debian/python-repoze.what/usr/lib/python2.7/site-packages/repoze/what/adapters
> copying repoze/what/adapters/__init__.py -> 
> /«PKGBUILDDIR»/debian/python-repoze.what/usr/lib/python2.7/site-packages/repoze/what/adapters
> Skipping installation of 
> /«PKGBUILDDIR»/debian/python-repoze.what/usr/lib/python2.7/site-packages/repoze/what/plugins/__init__.py
>  (namespace package)
> running install_egg_info
> Copying repoze.what.egg-info to 
> /«PKGBUILDDIR»/debian/python-repoze.what/usr/lib/python2.7/site-packages/repoze.what-1.0.9-py2.7.egg-info
> Installing 
> /«PKGBUILDDIR»/debian/python-repoze.what/usr/lib/python2.7/site-packages/repoze.what-1.0.9-py2.7-nspkg.pth
> running install_scripts
> dh_installdocs -ppython-repoze.what 
> cp: not writing through dangling symlink 
> '/«PKGBUILDDIR»/debian/python-repoze.what/usr/share/doc/python-repoze.what/html/_static/jquery.js'
> dh_installdocs: cd 'docs/build/html//..' && find 'html' \( -type f -or -type 
> l \) -and ! -empty -print0 | xargs -0 -I {} cp --parents -dp {} 
> /«PKGBUILDDIR»/debian/python-repoze.what/usr/share/doc/python-repoze.what 
> returned exit code 123
> make: *** [binary-install/python-repoze.what] Error 123

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/02/08/python-repoze.what_1.0.9-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 debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20140209160710.GA15007@Aeris.MIDGAR

Bug#738395: python-repoze.who: FTBFS: dh_installdocs: cd 'docs/.build/html//..' && find 'html' \( -type f -or -type l \) -and ! -empty -print0 | xargs -0 -I {} cp --parents -dp {} /«PKGBUILDDIR»/debia

2014-02-09 Thread David Suárez 
Source: python-repoze.who
Version: 1.0.18-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140208 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[1]: Entering directory `/«PKGBUILDDIR»/docs'
> mkdir -p .build/html .build/doctrees
> sphinx-build -b html -d .build/doctrees   . .build/html
> Running Sphinx v1.2.1
> running test
> running egg_info
> writing requirements to repoze.who.egg-info/requires.txt
> writing repoze.who.egg-info/PKG-INFO
> writing namespace_packages to repoze.who.egg-info/namespace_packages.txt
> writing top-level names to repoze.who.egg-info/top_level.txt
> writing dependency_links to repoze.who.egg-info/dependency_links.txt
> writing entry points to repoze.who.egg-info/entry_points.txt
> reading manifest file 'repoze.who.egg-info/SOURCES.txt'
> writing manifest file 'repoze.who.egg-info/SOURCES.txt'
> running build_ext
> .
> --
> Ran 213 tests in 0.062s
> 
> OK
> loading pickled environment... done
> building [html]: targets for 0 source files that are out of date
> updating environment: 0 added, 0 changed, 0 removed
> looking for now-outdated files... none found
> no targets are out of date.
> 
> Build finished. The HTML pages are in .build/html.
> make[1]: Leaving directory `/«PKGBUILDDIR»/docs'
> dh_link /usr/share/javascript/jquery/jquery.js \
>   /usr/share/doc/python-repoze.who/html/_static/jquery.js
> Adding cdbs dependencies to debian/python-repoze.who.substvars
> dh_installdirs -ppython-repoze.who 
> cd . && \
>   python setup.py install \
>   --root="/«PKGBUILDDIR»/debian/python-repoze.who/" \
>   --install-purelib=/usr/lib/python2.7/site-packages/ \
>   --prefix=/usr --no-compile -O0 
> --single-version-externally-managed 
> running install
> running build
> running build_py
> running egg_info
> writing requirements to repoze.who.egg-info/requires.txt
> writing repoze.who.egg-info/PKG-INFO
> writing namespace_packages to repoze.who.egg-info/namespace_packages.txt
> writing top-level names to repoze.who.egg-info/top_level.txt
> writing dependency_links to repoze.who.egg-info/dependency_links.txt
> writing entry points to repoze.who.egg-info/entry_points.txt
> reading manifest file 'repoze.who.egg-info/SOURCES.txt'
> writing manifest file 'repoze.who.egg-info/SOURCES.txt'
> running install_lib
> Skipping installation of 
> /«PKGBUILDDIR»/debian/python-repoze.who/usr/lib/python2.7/site-packages/repoze/__init__.py
>  (namespace package)
> copying repoze/who/interfaces.py -> 
> /«PKGBUILDDIR»/debian/python-repoze.who/usr/lib/python2.7/site-packages/repoze/who
> Skipping installation of 
> /«PKGBUILDDIR»/debian/python-repoze.who/usr/lib/python2.7/site-packages/repoze/who/__init__.py
>  (namespace package)
> copying repoze/who/middleware.py -> 
> /«PKGBUILDDIR»/debian/python-repoze.who/usr/lib/python2.7/site-packages/repoze/who
> copying repoze/who/config.py -> 
> /«PKGBUILDDIR»/debian/python-repoze.who/usr/lib/python2.7/site-packages/repoze/who
> copying repoze/who/classifiers.py -> 
> /«PKGBUILDDIR»/debian/python-repoze.who/usr/lib/python2.7/site-packages/repoze/who
> copying repoze/who/restrict.py -> 
> /«PKGBUILDDIR»/debian/python-repoze.who/usr/lib/python2.7/site-packages/repoze/who
> copying repoze/who/utils.py -> 
> /«PKGBUILDDIR»/debian/python-repoze.who/usr/lib/python2.7/site-packages/repoze/who
> Skipping installation of 
> /«PKGBUILDDIR»/debian/python-repoze.who/usr/lib/python2.7/site-packages/repoze/who/plugins/__init__.py
>  (namespace package)
> copying repoze/who/plugins/sql.py -> 
> /«PKGBUILDDIR»/debian/python-repoze.who/usr/lib/python2.7/site-packages/repoze/who/plugins
> copying repoze/who/plugins/auth_tkt.py -> 
> /«PKGBUILDDIR»/debian/python-repoze.who/usr/lib/python2.7/site-packages/repoze/who/plugins
> copying repoze/who/plugins/htpasswd.py -> 
> /«PKGBUILDDIR»/debian/python-repoze.who/usr/lib/python2.7/site-packages/repoze/who/plugins
> copying repoze/who/plugins/form.py -> 
> /«PKGBUILDDIR»/debian/python-repoze.who/usr/lib/python2.7/site-packages/repoze/who/plugins
> copying repoze/who/plugins/cookie.py -> 
> /«PKGBUILDDIR»/debian/python-repoze.who/usr/lib/python2.7/site-packages/repoze/who/plugins
> copying repoze/who/plugins/basicauth.py -> 
> /«PKGBUILDDIR»/debian/python-repoze.who/usr/lib/python2.7/site-packages/repoze/who/plugins
> copying repoze/who/plugins/tests/__init__.py -> 
> /«PKGBUILDDIR»/debian/python-repoze.who/usr/lib/python2.7/site-packages/repoze/who/plugins/tests
> copying repoze/who/plugins/tests/test_cookie.py -> 
> /«PKGBUILDDIR»/debian/python-repoze.

Bug#741806: pygresql: FTBFS: pgmodule.c:32:22: fatal error: postgres.h: No such file or directory

2014-03-16 Thread David Suárez 
Source: pygresql
Version: 1:4.0-3
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140315 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):
> x86_64-linux-gnu-gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 
> -Wall -Wstrict-prototypes -fPIC -Iinclude -I/usr/include/postgresql 
> -I/usr/include/python2.7 -c pgmodule.c -o 
> build/temp.linux-x86_64-2.7/pgmodule.o -O2
> pgmodule.c:32:22: fatal error: postgres.h: No such file or directory
>  #include "postgres.h"
>   ^
> compilation terminated.
> error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
> make: *** [build-arch-stamp] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/03/15/pygresql_4.0-3_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 debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140316125924.GA11893@Aeris.MIDGAR

Bug#741841: bzr-fastimport: FTBFS: ImportError: cannot import name binary_stream

2014-03-16 Thread David Suárez 
Source: bzr-fastimport
Version: 0.13.0-4
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140315 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[1]: Entering directory `/«PKGBUILDDIR»'
> BZR_PLUGINS_AT=fastimport@/«PKGBUILDDIR» bzr selftest -s bp.fastimport
> failed to open trace file: [Errno 2] No such file or directory: 
> '/sbuild-nonexistent/.bzr.log'
> bzr: ERROR: exceptions.ImportError: cannot import name binary_stream
> 
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/dist-packages/bzrlib/commands.py", line 930, in 
> exception_to_return_code
> return the_callable(*args, **kwargs)
>   File "/usr/lib/python2.7/dist-packages/bzrlib/commands.py", line 1121, in 
> run_bzr
> ret = run(*run_argv)
>   File "/usr/lib/python2.7/dist-packages/bzrlib/commands.py", line 673, in 
> run_argv_aliases
> return self.run(**all_cmd_args)
>   File "/usr/lib/python2.7/dist-packages/bzrlib/commands.py", line 697, in run
> return self._operation.run_simple(*args, **kwargs)
>   File "/usr/lib/python2.7/dist-packages/bzrlib/cleanup.py", line 136, in 
> run_simple
> self.cleanups, self.func, *args, **kwargs)
>   File "/usr/lib/python2.7/dist-packages/bzrlib/cleanup.py", line 166, in 
> _do_with_cleanups
> result = func(*args, **kwargs)
>   File "/usr/lib/python2.7/dist-packages/bzrlib/builtins.py", line 4201, in 
> run
> result = tests.selftest(**selftest_kwargs)
>   File "/usr/lib/python2.7/dist-packages/bzrlib/tests/__init__.py", line 
> 3734, in selftest
> suite = test_suite(keep_only, starting_with)
>   File "/usr/lib/python2.7/dist-packages/bzrlib/tests/__init__.py", line 
> 4225, in test_suite
> plugin_suite = plugin.test_suite()
>   File "/usr/lib/python2.7/dist-packages/bzrlib/plugin.py", line 555, in 
> test_suite
> return self.module.test_suite()
>   File "/«PKGBUILDDIR»/__init__.py", line 81, in test_suite
> return tests.test_suite()
>   File "/«PKGBUILDDIR»/tests/__init__.py", line 55, in test_suite
> return loader.loadTestsFromModuleNames(module_names)
>   File "/usr/lib/python2.7/dist-packages/bzrlib/tests/TestUtil.py", line 148, 
> in loadTestsFromModuleNames
> result.addTests(self.loadTestsFromModuleName(name))
>   File "/usr/lib/python2.7/dist-packages/bzrlib/tests/TestUtil.py", line 153, 
> in loadTestsFromModuleName
> module = pyutils.get_named_object(name)
>   File "/usr/lib/python2.7/dist-packages/bzrlib/pyutils.py", line 58, in 
> get_named_object
> __import__(module_name, globals(), locals(), [])
>   File "/«PKGBUILDDIR»/tests/test_exporter.py", line 24, in 
> from bzrlib.plugins.fastimport.exporter import (
>   File "/«PKGBUILDDIR»/exporter.py", line 67, in 
> from fastimport.helpers import (
> ImportError: cannot import name binary_stream
> 
> bzr 2.7.0dev1 on python 2.7.6 (Linux-2.6.32-5-xen-amd64-x86_64-with-debian-
> jessie-sid)
> arguments: ['/usr/bin/bzr', 'selftest', '-s', 'bp.fastimport']
> plugins: bash_completion[2.7.0dev1], changelog_merge[2.7.0dev1],
> fastimport[0.13.0], grep[2.7.0dev1], launchpad[2.7.0dev1],
> netrc_credential_store[2.7.0dev1], news_merge[2.7.0dev1],
> po_merge[2.7.0dev1], weave_fmt[2.7.0dev1]
> encoding: 'ascii', fsenc: 'utf8', lang: None
> 
> *** Bazaar has encountered an internal error.  This probably indicates a
> bug in Bazaar.  You can help us fix it by filing a bug report at
> https://bugs.launchpad.net/bzr/+filebug
> including this traceback and a description of the problem.
> make[1]: *** [override_dh_auto_test] Error 4

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/03/15/bzr-fastimport_0.13.0-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 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 debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140316131747.GA13116@Aeris.MIDGAR

Bug#750274: socks4-server: FTBFS: make[2]: *** No rule to make target '-lident', needed by 'sockd'. Stop.

2014-06-02 Thread David Suárez 
Source: socks4-server
Version: 4.3.beta2-18
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140601 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[2]: Entering directory '/«PKGBUILDDIR»/sockd'
> /«PKGBUILDDIR»/sockd
> gcc -I../include -g -DLINUX   -c -o sockd_ckcf.o sockd_ckcf.c
> gcc -I../include -g -DLINUX   -c -o sockd_ckrt.o sockd_ckrt.c
> sockd_ckrt.c: In function 'sockd_ckrt':
> sockd_ckrt.c:24:2: warning: incompatible implicit declaration of built-in 
> function 'exit' [enabled by default]
>   exit(1);
>   ^
> gcc -I../include -g -DLINUX   -c -o sockd_getspcmd.o sockd_getspcmd.c
> gcc -I../include -g -DLINUX   -c -o sockd_fail.o sockd_fail.c
> sockd_fail.c: In function 'sockd_fail':
> sockd_fail.c:16:2: warning: incompatible implicit declaration of built-in 
> function 'exit' [enabled by default]
>   exit(1);
>   ^
> gcc -I../include -g -DLINUX   -c -o setproctitle.o setproctitle.c
> gcc -I../include -g -DLINUX   -c -o DoConnect.o DoConnect.c
> DoConnect.c: In function 'DoConnect':
> DoConnect.c:35:2: warning: incompatible implicit declaration of built-in 
> function 'bzero' [enabled by default]
>   bzero((char *)&sin, sizeof(sin));
>   ^
> gcc -I../include -g -DLINUX   -c -o DoNewBind.o DoNewBind.c
> DoNewBind.c: In function 'DoNewBind':
> DoNewBind.c:50:2: warning: incompatible implicit declaration of built-in 
> function 'bzero' [enabled by default]
>   bzero((char *)&sin, sizeof(sin));
>   ^
> DoNewBind.c:139:4: warning: incompatible implicit declaration of built-in 
> function 'exit' [enabled by default]
> exit(1);
> ^
> gcc -I../include -g -DLINUX -DSOCKSIFIED_SOCKD -c -o RDoConnect.o 
> DoConnect.c
> DoConnect.c: In function 'RDoConnect':
> DoConnect.c:35:2: warning: incompatible implicit declaration of built-in 
> function 'bzero' [enabled by default]
>   bzero((char *)&sin, sizeof(sin));
>   ^
> gcc -I../include -g -DLINUX -DSOCKSIFIED_SOCKD -c -o RDoNewBind.o 
> DoNewBind.c 
> DoNewBind.c: In function 'RDoNewBind':
> DoNewBind.c:50:2: warning: incompatible implicit declaration of built-in 
> function 'bzero' [enabled by default]
>   bzero((char *)&sin, sizeof(sin));
>   ^
> DoNewBind.c:76:2: warning: incompatible implicit declaration of built-in 
> function 'strcpy' [enabled by default]
>   strcpy(socks_srcsh.user, srcshp->user);
>   ^
> rm -f libsockd.a
> ar rc libsockd.a sockd_ckcf.o sockd_ckrt.o sockd_getspcmd.o sockd_fail.o 
> setproctitle.o DoConnect.o DoNewBind.o RDoConnect.o RDoNewBind.o
> ranlib libsockd.a
> gcc -I../include -g -DLINUX   -c -o sockd.o sockd.c
> sockd.c: In function 'readConfig':
> sockd.c:95:3: warning: incompatible implicit declaration of built-in function 
> 'exit' [enabled by default]
>exit(1);
>^
> sockd.c:112:3: warning: incompatible implicit declaration of built-in 
> function 'exit' [enabled by default]
>exit(1);
>^
> sockd.c: In function 'die':
> sockd.c:163:2: warning: incompatible implicit declaration of built-in 
> function 'exit' [enabled by default]
>   exit(1);
>   ^
> sockd.c: In function 'main':
> sockd.c:293:3: warning: incompatible implicit declaration of built-in 
> function 'exit' [enabled by default]
>exit(1);
>^
> sockd.c:349:3: warning: incompatible implicit declaration of built-in 
> function 'exit' [enabled by default]
>exit(1);
>^
> sockd.c:353:3: warning: incompatible implicit declaration of built-in 
> function 'exit' [enabled by default]
>exit(1);
>^
> sockd.c:424:3: warning: incompatible implicit declaration of built-in 
> function 'exit' [enabled by default]
>exit(1);
>^
> sockd.c:432:3: warning: incompatible implicit declaration of built-in 
> function 'exit' [enabled by default]
>exit(1);
>^
> sockd.c:438:3: warning: incompatible implicit declaration of built-in 
> function 'exit' [enabled by default]
>exit(1);
>^
> sockd.c:444:3: warning: incompatible implicit declaration of built-in 
> function 'exit' [enabled by default]
>exit(1);
>^
> sockd.c:456:3: warning: incompatible implicit declaration of built-in 
> function 'exit' [enabled by default]
>exit(1);
>^
> sockd.c:477:4: warning: incompatible implicit declaration of built-in 
> function 'exit' [enabled by default]
> exit(1);
> ^
> sockd.c:492:4: warning: incompatible implicit declaration of built-in 
> function 'exit' [enabled by default]
> exit(1);
> ^
> sockd.c:499:4: warning: incompatible implicit declaration of built-in 
> function 'exit' [enabled by default]
> exit(1);
> ^
> sockd.c:507:4: warning: incompatible implicit declaration of built-in 
> function 'exit' [enabled by default]
> exit(1);
> ^
> sockd.c:541:3: warning: incompatible implicit declaration of built-in 
> function 'exit' [enabled by default]
>exit(1);
>

Bug#750298: xenwatch: FTBFS: Make.config:1: *** empty variable name.

2014-06-02 Thread David Suárez 
Source: xenwatch
Version: 0.5.4-3
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140601 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):
>  fakeroot debian/rules clean
> dh clean
>dh_testdir
>dh_auto_clean
> make[1]: Entering directory '/«PKGBUILDDIR»'
> Make.config:1: *** empty variable name.  Stop.
> make[1]: Leaving directory '/«PKGBUILDDIR»'
> dh_auto_clean: make -j1 distclean returned exit code 2
> make: *** [clean] Error 2

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/06/01/xenwatch_0.5.4-3_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 debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140602191721.GA13042@Sephirot.MIDGAR

Bug#750320: canna: FTBFS: /bin/sh: 1: platex: not found

2014-06-02 Thread David Suárez 
Source: canna
Version: 3.7p3-12
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140601 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[2]: Entering directory '/«PKGBUILDDIR»/doc/man/guide/tex'
> (echo "s%@(cannaBinDir)%/usr//bin%g"; \
>  echo "s%@(cannaLibDir)%/etc/canna%g"; \
>  echo "s%@(cannaIncDir)%/usr//include/canna%g"; \
>  echo "s%@(UnixSockDir)%/tmp/.iroha_unix%g"; \
>  echo "s%@(UnixSockName)%IROHA%g"; \
>  echo "s%@(AccessFile)%/etc/hosts.canna%g"; \
>  echo "s%@(DicDir)%/var/lib/canna/dic%g"; \
>  echo "s%@(ErrDir)%/var/log/canna%g") > ../../../../misc/manual.sed
> sed -f ../../../../misc/manual.sed canna-dist.tex > canna.tex
> gcc -g -O2 -fno-strict-aliasing-I../../../../include -Dlinux 
> -D__amd64__ -D_POSIX_C_SOURCE=199309L
> -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE 
> -D_SVID_SOURCE -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64
>-DFUNCPROTO=15 -DNARROWPROTO   -c -o cannaindex.o cannaindex.c
> rm -f cannaindex
> gcc -o cannaindex -g -O2 -fno-strict-aliasing   cannaindex.o   
> echo 'DUMMY' > candex.tex
> platex --kanji=euc canna.tex
> /bin/sh: 1: platex: not found
> make[2]: *** [canna.dvi] Error 127

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/06/01/canna_3.7p3-12_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 debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140602183806.GA9356@Sephirot.MIDGAR

Bug#753178: hfsutils: FTBFS: dpkg-source: error: expected ^--- in line 1 of diff `hfsutils-3.2.6/debian/patches/man-macros.diff'

2014-06-29 Thread David Suárez 
Source: hfsutils
Version: 3.2.6-12
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140628 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):
> Unpack source
> ─
> 
> gpgv: keyblock resource `/sbuild-nonexistent/.gnupg/trustedkeys.gpg': file 
> open error
> gpgv: Signature made Thu Mar 14 20:53:18 2013 UTC using DSA key ID 0F932C9C
> gpgv: Can't check signature: public key not found
> dpkg-source: warning: failed to verify signature on ./hfsutils_3.2.6-12.dsc
> dpkg-source: info: extracting hfsutils in hfsutils-3.2.6
> dpkg-source: info: unpacking hfsutils_3.2.6.orig.tar.gz
> tar: A lone zero block at 2060
> dpkg-source: info: unpacking hfsutils_3.2.6-12.debian.tar.gz
> dpkg-source: info: applying 01_fix_build-system.dpatch
> dpkg-source: info: applying 280310_ftbfs_include_gcc3.4.dpatch
> dpkg-source: info: applying hattrib-man.diff
> dpkg-source: error: expected ^--- in line 1 of diff 
> `hfsutils-3.2.6/debian/patches/man-macros.diff'
> dpkg-source: info: applying man-macros.diff
> dpkg-source: info: fuzz is not allowed when applying patches
> dpkg-source: info: if patch 'man-macros.diff' is correctly applied by quilt, 
> use 'quilt refresh' to update it
> FAILED [dpkg-source died]

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/06/28/hfsutils_3.2.6-12_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 debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140629180438.GA18451@Sephirot.MIDGAR

Bug#763255: freeimage: FTBFS: transupp.c:900: undefined reference to `jpeg_core_output_dimensions'

2014-09-28 Thread David Suárez 
Source: freeimage
Version: 3.15.4-3
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140926 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):
> g++ -shared -Wl,-soname,libfreeimage.so.3 -Wl,-z,defs -Wl,-z,relro -o 
> libfreeimage-3.15.4.so ./Source/FreeImage/BitmapAccess.o 
> ./Source/FreeImage/ColorLookup.o ./Source/FreeImage/FreeImage.o 
> ./Source/FreeImage/FreeImageC.o ./Source/FreeImage/FreeImageIO.o 
> ./Source/FreeImage/GetType.o ./Source/FreeImage/MemoryIO.o 
> ./Source/FreeImage/PixelAccess.o ./Source/FreeImage/J2KHelper.o 
> ././Source/FreeImage/MNGHelper.o ./Source/FreeImage/Plugin.o 
> ./Source/FreeImage/PluginBMP.o ./Source/FreeImage/PluginCUT.o 
> ./Source/FreeImage/PluginDDS.o ./Source/FreeImage/PluginEXR.o 
> ./Source/FreeImage/PluginG3.o ./Source/FreeImage/PluginGIF.o 
> ./Source/FreeImage/PluginHDR.o ./Source/FreeImage/PluginICO.o 
> ./Source/FreeImage/PluginIFF.o ./Source/FreeImage/PluginJ2K.o 
> ././Source/FreeImage/PluginJNG.o ./Source/FreeImage/PluginJP2.o 
> ./Source/FreeImage/PluginJPEG.o ./Source/FreeImage/PluginKOALA.o 
> ./Source/FreeImage/PluginMNG.o ./Source/FreeImage/PluginPCD.o 
> ./Source/FreeImage/PluginPCX.o ./Source/FreeImage/PluginPFM.o 
> ./Source/FreeImage/PluginPICT.o ./Source/FreeImage/PluginPNG.o 
> ./Source/FreeImage/PluginPNM.o ./Source/FreeImage/PluginPSD.o 
> ./Source/FreeImage/PluginRAS.o ./Source/FreeImage/PluginRAW.o 
> ./Source/FreeImage/PluginSGI.o ./Source/FreeImage/PluginTARGA.o 
> ./Source/FreeImage/PluginTIFF.o ./Source/FreeImage/PluginWBMP.o 
> ./Source/FreeImage/PluginXBM.o ./Source/FreeImage/PluginXPM.o 
> ./Source/FreeImage/PSDParser.o ./Source/FreeImage/TIFFLogLuv.o 
> ./Source/FreeImage/Conversion.o ./Source/FreeImage/Conversion16_555.o 
> ./Source/FreeImage/Conversion16_565.o ./Source/FreeImage/Conversion24.o 
> ./Source/FreeImage/Conversion32.o ./Source/FreeImage/Conversion4.o 
> ./Source/FreeImage/Conversion8.o ./Source/FreeImage/ConversionFloat.o 
> ./Source/FreeImage/ConversionRGB16.o ./Source/FreeImage/ConversionRGBF.o 
> ./Source/FreeImage/ConversionType.o ./Source/FreeImage/ConversionUINT16.o 
> ./Source/FreeImage/Halftoning.o ./Source/FreeImage/tmoColorConvert.o 
> ./Source/FreeImage/tmoDrago03.o ./Source/FreeImage/tmoFattal02.o 
> ./Source/FreeImage/tmoReinhard05.o ./Source/FreeImage/ToneMapping.o 
> ./Source/FreeImage/NNQuantizer.o ./Source/FreeImage/WuQuantizer.o 
> ./Source/DeprecationManager/Deprecated.o 
> ./Source/DeprecationManager/DeprecationMgr.o ./Source/FreeImage/CacheFile.o 
> ./Source/FreeImage/MultiPage.o ./Source/FreeImage/ZLibInterface.o 
> ./Source/Metadata/Exif.o ./Source/Metadata/FIRational.o 
> ./Source/Metadata/FreeImageTag.o ./Source/Metadata/IPTC.o 
> ./Source/Metadata/TagConversion.o ./Source/Metadata/TagLib.o 
> ./Source/Metadata/XTIFF.o ./Source/FreeImageToolkit/Background.o 
> ./Source/FreeImageToolkit/BSplineRotate.o 
> ./Source/FreeImageToolkit/Channels.o 
> ./Source/FreeImageToolkit/ClassicRotate.o ./Source/FreeImageToolkit/Colors.o 
> ./Source/FreeImageToolkit/CopyPaste.o ./Source/FreeImageToolkit/Display.o 
> ./Source/FreeImageToolkit/Flip.o ./Source/FreeImageToolkit/JPEGTransform.o 
> ./Source/FreeImageToolkit/MultigridPoissonSolver.o 
> ./Source/FreeImageToolkit/Rescale.o ./Source/FreeImageToolkit/Resize.o 
> Source/LibJPEG/transupp.o -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -fPIC -fexceptions -fvisibility=hidden 
> -Wno-ctor-dtor-privacy -I. -ISource -ISource/Metadata 
> -ISource/FreeImageToolkit -pthread -I/usr/include/OpenEXR 
> -I/usr/include/libraw -I/usr/include/libpng12 -I/usr/include/x86_64-linux-gnu 
>  -lstdc++ -ljpeg -lmng -lopenjpeg -L/usr/lib/x86_64-linux-gnu -L/usr/lib -lz 
> -lIlmImf -lz -pthread -lImath -lHalf -lIex -lIlmThread -lraw -lstdc++ 
> -fopenmp -llcms2 -lpng12 -ltiff  -lm
> Source/LibJPEG/transupp.o: In function `jtransform_request_workspace':
> /«PKGBUILDDIR»/Source/LibJPEG/transupp.c:900: undefined reference to 
> `jpeg_core_output_dimensions'
> collect2: error: ld returned 1 exit status

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/09/26/freeimage_3.15.4-3_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 debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140928164348.GA29800@Sephirot.MIDGAR

Bug#763242: kst: FTBFS: :0:1: error: macro names must be identifiers

2014-09-28 Thread David Suárez 
Source: kst
Version: 2.0.3-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140926 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 
> [  0%] Generating kstcore_pch.h.gch
> cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/libkst && /usr/bin/cmake -E remove 
> /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/libkst/kstcore_pch.h.gch
> cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/libkst && /usr/bin/c++ 
> -DKST_HAVE_SVN_REVISION_H  -DQT_GUI_LIB -DQT_CORE_LIB -DBUILD_KSTCORE -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 
> -Wall -lrt -g -fPIC -D -I /usr/include/qt4 -I /usr/include/qt4/QtGui -I 
> /usr/include/qt4/QtCore -I /«PKGBUILDDIR»/obj-x86_64-linux-gnu -I 
> /usr/include/qt4/QtDesigner -I /usr/include/qt4/QtDeclarative -I 
> /usr/include/qt4/QtScriptTools -I /usr/include/qt4/QtDBus -I 
> /usr/include/qt4/QtDesigner -I /usr/include/qt4/QtXml -I 
> /usr/include/qt4/QtSql -I /usr/include/qt4/QtOpenGL -I 
> /usr/include/qt4/QtNetwork -I /usr/include/qt4/QtXmlPatterns -I 
> /usr/include/qt4/QtHelp -I /usr/include/qt4/QtUiTools -I 
> /usr/include/qt4/QtTest -I /usr/include/qt4/QtScript -I 
> /usr/include/qt4/QtSvg -I /usr/include/qt4/Qt3Support -I 
> /usr/include/qt4/QtGui -I /usr/include/qt4/QtCore -I 
> /usr/share/qt4/mkspecs/default -I /usr/include/qt4 -I /usr/include/qt4/QtCore 
> -I /«PKGBUILDDIR»/src/libkst -I 
> /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/libkst -c 
> /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/libkst/kstcore_pch.h -o 
> /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/libkst/kstcore_pch.h.gch
> :0:1: error: macro names must be identifiers
> make[4]: *** [src/libkst/kstcore_pch.h.gch] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/09/26/kst_2.0.3-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 debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140928164518.GA30003@Sephirot.MIDGAR

Bug#713540: ddccontrol: FTBFS: ld: notebook.o: undefined reference to symbol 'round@@GLIBC_2.2.5'

2013-06-22 Thread David Suárez 
Source: ddccontrol
Version: 0.4.2-10
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
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 -I/usr/include/libxml2 -pthread -I/usr/include/gtk-2.0 
> -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 
> -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 
> -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 
> -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libdrm 
> -I/usr/include/harfbuzz -g -O2 -Wall -DDATADIR=\"/usr/share/ddccontrol-db\" 
> -DBINDIR=\"/usr/bin\" -o .libs/gddccontrol -pthread main.o notebook.o 
> gprofile.o fspatterns.o  -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 
> -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 
> /usr/lib/x86_64-linux-gnu/libcairo.so -lpango-1.0 
> /usr/lib/x86_64-linux-gnu/libfreetype.so -lfontconfig -lgobject-2.0 
> -lgthread-2.0 -lglib-2.0 ../lib/.libs/libddccontrol.so -lxml2 -lpci
> /usr/bin/ld: notebook.o: undefined reference to symbol 'round@@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/ddccontrol_0.4.2-10_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 debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130622115708.GA7926@Aeris.MIDGAR

Bug#713596: gdome2: FTBFS: gdome-xml-documentt.c:345:35: error: dereferencing pointer to incomplete type

2013-06-22 Thread David Suárez 
Source: gdome2
Version: 0.8.1+debian-5
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
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.

Relevant part:
> /bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
> -I../.. -I../../libgdome -I../../libgdome/gdomecore -I../../libgdome/events 
> -I../../libgdome/xpath -I/usr/include/libxml2 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include   -Wall -ansi -g -O2 -MT 
> gdome-xml-documentt.lo -MD -MP -MF .deps/gdome-xml-documentt.Tpo -c -o 
> gdome-xml-documentt.lo gdome-xml-documentt.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -I../../libgdome 
> -I../../libgdome/gdomecore -I../../libgdome/events -I../../libgdome/xpath 
> -I/usr/include/libxml2 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wall -ansi -g -O2 -MT 
> gdome-xml-documentt.lo -MD -MP -MF .deps/gdome-xml-documentt.Tpo -c 
> gdome-xml-documentt.c  -fPIC -DPIC -o .libs/gdome-xml-documentt.o
> gdome-xml-documentt.c: In function 'gdome_xml_dt_internalSubset':
> gdome-xml-documentt.c:345:35: error: dereferencing pointer to incomplete type
>   ret = g_strndup (out_buff->buffer->content, out_buff->buffer->use);
>^
> gdome-xml-documentt.c:345:62: error: dereferencing pointer to incomplete type
>   ret = g_strndup (out_buff->buffer->content, out_buff->buffer->use);
>   ^
> make[4]: *** [gdome-xml-documentt.lo] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/20/gdome2_0.8.1+debian-5_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 debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130622132849.GA12834@Aeris.MIDGAR

Bug#713641: l7-filter-userspace: FTBFS: l7-queue.cpp:199:34: error: invalid conversion from 'char**' to 'unsigned char**' [-fpermissive]

2013-06-22 Thread David Suárez 
Source: l7-filter-userspace
Version: 0.12-beta1-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
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.

Relevant part:
> g++ -DHAVE_CONFIG_H -I. -g -O2 -c -o l7-queue.o l7-queue.cpp
> l7-queue.cpp: In function 'int l7_queue_cb(nfq_q_handle*, nfgenmsg*, 
> nfq_data*, void*)':
> l7-queue.cpp:80:12: warning: 'int nfq_set_verdict_mark(nfq_q_handle*, 
> u_int32_t, u_int32_t, u_int32_t, u_int32_t, const unsigned char*)' is 
> deprecated (declared at 
> /usr/include/libnetfilter_queue/libnetfilter_queue.h:85) 
> [-Wdeprecated-declarations]
>  return nfq_set_verdict_mark(qh, id, NF_ACCEPT, htonl(wholemark), 0, 
> NULL);
> ^
> l7-queue.cpp:80:77: warning: 'int nfq_set_verdict_mark(nfq_q_handle*, 
> u_int32_t, u_int32_t, u_int32_t, u_int32_t, const unsigned char*)' is 
> deprecated (declared at 
> /usr/include/libnetfilter_queue/libnetfilter_queue.h:85) 
> [-Wdeprecated-declarations]
>  return nfq_set_verdict_mark(qh, id, NF_ACCEPT, htonl(wholemark), 0, 
> NULL);
>  ^
> l7-queue.cpp: In member function 'u_int32_t 
> l7_queue::handle_packet(nfq_data*, nfq_q_handle*)':
> l7-queue.cpp:199:34: error: invalid conversion from 'char**' to 'unsigned 
> char**' [-fpermissive]
>ret = nfq_get_payload(tb, &data);
>   ^
> In file included from l7-queue.cpp:55:0:
> /usr/include/libnetfilter_queue/libnetfilter_queue.h:119:12: error:   
> initializing argument 2 of 'int nfq_get_payload(nfq_data*, unsigned char**)' 
> [-fpermissive]
>  extern int nfq_get_payload(struct nfq_data *nfad, unsigned char **data);
> ^
> l7-queue.cpp:281:10: warning: 'int nfq_set_verdict_mark(nfq_q_handle*, 
> u_int32_t, u_int32_t, u_int32_t, u_int32_t, const unsigned char*)' is 
> deprecated (declared at 
> /usr/include/libnetfilter_queue/libnetfilter_queue.h:85) 
> [-Wdeprecated-declarations]
>return nfq_set_verdict_mark(qh, id, NF_ACCEPT, 
>   ^
> l7-queue.cpp:282:77: warning: 'int nfq_set_verdict_mark(nfq_q_handle*, 
> u_int32_t, u_int32_t, u_int32_t, u_int32_t, const unsigned char*)' is 
> deprecated (declared at 
> /usr/include/libnetfilter_queue/libnetfilter_queue.h:85) 
> [-Wdeprecated-declarations]
>htonl((mark< NULL);
>  ^
> make[2]: *** [l7-queue.o] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/20/l7-filter-userspace_0.12-beta1-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 debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130622133532.GA13228@Aeris.MIDGAR

Bug#713651: ifrit: FTBFS: ld: CMakeFiles/ifrit.dir/«PKGBUILDDIR»/shells/generic/iggrenderwindow.o: undefined reference to symbol 'glGetBooleanv'

2013-06-22 Thread David Suárez 
Source: ifrit
Version: 3.3.4-4
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
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:
> /usr/bin/c++ -Wno-deprecated -O3 -DNDEBUG  -Wl,--as-needed  
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/configure/iversion.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/configure/ishellfactory.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/configure/ifrit.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/configure/iextensionfactory.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/configure/iextensionbuilder.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/configure/iedition.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/iparticlesplitter.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/isystem.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/iwriter.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/ivolumeviewsubject.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/ivolumedataconverter.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/iviewsubjectpipelinedatamanager.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/iviewsubjectpipeline.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/iviewsubjectparallelpipeline.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/iviewsubjectobserver.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/iviewsubjectcomponent.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/iviewsubject.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/iviewobjectfamily.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/iviewobject.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/iviewmodule.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/ivectortextsubject.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/ivectorglyphfilter.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/ivectorfieldviewsubject.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/ivectorfieldstreamlinepipeline.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/ivectorfieldglyphpipeline.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/iuniformgridfileloader.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/iuniformgriddata.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/itransform.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/itextsubject.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/itextactor.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/itensorglyphfilter.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/itensorfieldviewsubject.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/itensorfieldpipeline.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/isurfaceviewsubject.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/isurfacepipeline.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/istring.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/istreamlinefilter.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/istereoimagearray.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/istereoimage.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/isolidviewsubject.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/isolidobjectsource.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/ismoothpolydatafilter2.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/ismoothpolydatafilter.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/ishiftpolydatafilter.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/ishell.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/iscriptkit.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/iscript.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/iruler.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/iresampleimagedatafilter.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/ireplicatedvolume.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/ireplicatedpolydata.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/ireplicatedgriddata.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/ireplicatedelement.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/ireplicatedactor.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/irendertoolbackground.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/irendertool.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/ireducepolydatafilter2.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/ireducepolydatafilter.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/irangemapping.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/irangecollection.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/iprobefilter.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/ipostscriptwriter.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/iposition.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/ipointglyph.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/ipointer.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/ipiecewisefunction.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/ipicker.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/iparticlesviewsubject.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/iparticleprobefilter.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/iparticlegrouppipeline.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/iparticlegroup.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/iparticlefileloader.o 
> CMakeFiles/ifrit.dir/«PKGBUILDDIR»/core/iparticledownsampleiterator.o 
> CMakeFiles/ifrit.di

Bug#713611: lightspeed: FTBFS: lightspeed.h:69:23: fatal error: gtk/gtkgl.h: No such file or directory

2013-06-22 Thread David Suárez 
Source: lightspeed
Version: 1.2a-9
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
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.

Relevant part:
> gcc -DHAVE_CONFIG_H -I. -I. -I..  -D_FORTIFY_SOURCE=2 
> -DLOCALEDIR=\"/usr/share/locale\" -DDATADIR=\"/usr/share\" 
> -D_FORTIFY_SOURCE=2 -pthread -I/usr/include/gtk-2.0 
> -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 
> -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 
> -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 
> -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libdrm 
> -I/usr/include/harfbuzz  -g -O2 -fstack-protector 
> --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c -o 
> lightspeed-animation.o `test -f 'animation.c' || echo './'`animation.c
> In file included from animation.c:26:0:
> lightspeed.h:69:23: fatal error: gtk/gtkgl.h: No such file or directory
>  #include 
>^
> compilation terminated.
> make[4]: *** [lightspeed-animation.o] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/20/lightspeed_1.2a-9_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 debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130622133854.GA13549@Aeris.MIDGAR

Bug#713628: prelink: FTBFS: (.text+0x1d8): undefined reference to `pthread_atfork'

2013-06-22 Thread David Suárez 
Source: prelink
Version: 0.0.20090925-7
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
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.

Relevant part:
> gcc -D_GNU_SOURCE -DHAVE_CONFIG_H -Wall -Wno-pointer-sign -I. -I../../src 
> -I.. -I../../gelfx -DSBINDIR='"//sbin"'  -Wall -Wno-pointer-sign -g -O2 -c 
> ../../src/sha.c
> ../../src/sha.c: In function 'sha_finish_ctx':
> ../../src/sha.c:92:3: warning: dereferencing type-punned pointer will break 
> strict-aliasing rules [-Wstrict-aliasing]
>*(md5_uint32 *) &ctx->buffer[bytes + pad + 4] = NOTSWAP (ctx->total[0] << 
> 3);
>^
> ../../src/sha.c:93:3: warning: dereferencing type-punned pointer will break 
> strict-aliasing rules [-Wstrict-aliasing]
>*(md5_uint32 *) &ctx->buffer[bytes + pad] = NOTSWAP ((ctx->total[1] << 3) |
>^
> /bin/bash ../libtool  --tag=CC   --mode=link gcc -Wall -Wno-pointer-sign -g 
> -O2 -all-static  -o prelink cache.o conflict.o cxx.o doit.o exec.o 
> execle_open.o get.o gather.o layout.o main.o prelink.o reloc.o space.o undo.o 
> undoall.o verify.o canonicalize.o md5.o sha.o checksum.o data.o dso.o 
> dwarf2.o fptr.o hashtab.o mdebug.o stabs.o crc32.o arch-i386.o arch-alpha.o 
> arch-ppc.o arch-ppc64.o arch-sparc.o arch-sparc64.o arch-x86_64.o arch-mips.o 
> arch-s390.o arch-s390x.o arch-arm.o arch-sh.o arch-ia64.o  -lselinux -lelf 
> libtool: link: gcc -Wall -Wno-pointer-sign -g -O2 -static -o prelink cache.o 
> conflict.o cxx.o doit.o exec.o execle_open.o get.o gather.o layout.o main.o 
> prelink.o reloc.o space.o undo.o undoall.o verify.o canonicalize.o md5.o 
> sha.o checksum.o data.o dso.o dwarf2.o fptr.o hashtab.o mdebug.o stabs.o 
> crc32.o arch-i386.o arch-alpha.o arch-ppc.o arch-ppc64.o arch-sparc.o 
> arch-sparc64.o arch-x86_64.o arch-mips.o arch-s390.o arch-s390x.o arch-arm.o 
> arch-sh.o arch-ia64.o  -lselinux -lelf
> /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libselinux.a(procattr.o):
>  In function `init_procattr':
> (.text+0x1d8): undefined reference to `pthread_atfork'
> collect2: error: ld returned 1 exit status

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/20/prelink_0.0.20090925-7_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 debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130622131517.GA12262@Aeris.MIDGAR

Bug#713594: mssh: FTBFS: pango-font.h:380:33: error: ISO C restricts enumerator values to range of 'int' [-Wpedantic]

2013-06-22 Thread David Suárez 
Source: mssh
Version: 1.2-3
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
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.

Relevant part:
> gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/gtk-2.0 
> -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 
> -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 
> -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 
> -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libdrm 
> -I/usr/include/harfbuzz -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/vte-0.0
> -D_FORTIFY_SOURCE=2 -pedantic-errors -Werror -Wall -Wfatal-errors 
> -Wwrite-strings -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat 
> -Werror=format-security -c mssh.c
> In file included from /usr/include/pango-1.0/pango/pango-attributes.h:25:0,
>  from /usr/include/pango-1.0/pango/pango.h:25,
>  from /usr/include/gtk-2.0/gdk/gdktypes.h:37,
>  from /usr/include/gtk-2.0/gdk/gdkscreen.h:32,
>  from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:31,
>  from /usr/include/gtk-2.0/gdk/gdk.h:32,
>  from /usr/include/gtk-2.0/gtk/gtk.h:32,
>  from mssh.c:7:
> /usr/include/pango-1.0/pango/pango-font.h:380:33: error: ISO C restricts 
> enumerator values to range of 'int' [-Wpedantic]
>PANGO_GLYPH_INVALID_INPUT =   ((PangoGlyph)0x),
>  ^
> compilation terminated due to -Wfatal-errors.
> make[3]: *** [mssh.o] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/06/20/mssh_1.2-3_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 debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130622134226.GA13764@Aeris.MIDGAR

Bug#713771: xdemorse: FTBFS: ld: detect.o: undefined reference to symbol 'sincos@@GLIBC_2.2.5'

2013-06-22 Thread David Suárez 
Source: xdemorse
Version: 1.3-6
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
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  -g -O2   -o xdemorse main.o cat.o detect.o decode.o display.o fft.o 
> sound.o support.o interface.o callbacks.o -lgtk-x11-2.0 -lgdk-x11-2.0 
> -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo 
> -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lglib-2.0   
> /usr/bin/ld: detect.o: undefined reference to symbol 'sincos@@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/xdemorse_1.3-6_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 debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130622125503.GA11574@Aeris.MIDGAR

Bug#713673: libcdaudio: FTBFS: configure.ac:20: error: automatic de-ANSI-fication support has been removed

2013-06-22 Thread David Suárez 
Source: libcdaudio
Version: 0.99.12p2-12
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
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.

Relevant part:
>  debian/rules build
> dh build --with autoreconf --parallel
>dh_testdir -O--parallel
>dh_autoreconf -O--parallel
> configure.ac:20: error: automatic de-ANSI-fication support has been removed
> /usr/share/aclocal-1.13/obsolete.m4:26: AM_C_PROTOTYPES is expanded from...
> configure.ac:20: the top level
> autom4te: /usr/bin/m4 failed with exit status: 1
> aclocal: error: echo failed with exit status: 1
> autoreconf: aclocal failed with exit status: 1
> dh_autoreconf: autoreconf -f -i returned exit code 1
> make: *** [build] Error 2

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/20/libcdaudio_0.99.12p2-12_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 debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130622133714.GA13336@Aeris.MIDGAR

Bug#713704: gtkglextmm: FTBFS: ld: cannot find -lcposix

2013-06-22 Thread David Suárez 
Source: gtkglextmm
Version: 1.2.0-6
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
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.

Relevant part:
> g++: fatal error: no input files
> compilation terminated.
> configure:3507: $? = 4
> configure:3510: checking whether we are using the GNU C++ compiler
> configure:3534: g++ -c -g -O2 -fstack-protector --param=ssp-buffer-size=4 
> -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 conftest.cc >&5
> configure:3540: $? = 0
> configure:3544: test -z 
>|| test ! -s conftest.err
> configure:3547: $? = 0
> configure:3550: test -s conftest.o
> configure:3553: $? = 0
> configure:3566: result: yes
> configure:3572: checking whether g++ accepts -g
> configure:3593: g++ -c -g -D_FORTIFY_SOURCE=2 conftest.cc >&5
> configure:3599: $? = 0
> configure:3603: test -z 
>|| test ! -s conftest.err
> configure:3606: $? = 0
> configure:3609: test -s conftest.o
> configure:3612: $? = 0
> configure:3623: result: yes
> configure:3665: g++ -c -g -O2 -fstack-protector --param=ssp-buffer-size=4 
> -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 conftest.cc >&5
> configure:3671: $? = 0
> configure:3675: test -z 
>|| test ! -s conftest.err
> configure:3678: $? = 0
> configure:3681: test -s conftest.o
> configure:3684: $? = 0
> configure:3710: g++ -c -g -O2 -fstack-protector --param=ssp-buffer-size=4 
> -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 conftest.cc >&5
> conftest.cc: In function 'int main()':
> conftest.cc:13:9: error: 'exit' was not declared in this scope
>  exit (42);
>  ^
> configure:3716: $? = 1
> configure: failed program was:
> | /* confdefs.h.  */
> | 
> | #define PACKAGE_NAME "gtkglextmm"
> | #define PACKAGE_TARNAME "gtkglextmm"
> | #define PACKAGE_VERSION "1.2.0"
> | #define PACKAGE_STRING "gtkglextmm 1.2.0"
> | #define PACKAGE_BUGREPORT "gtkglext-deve...@lists.sourceforge.net"
> | /* end confdefs.h.  */
> | 
> | int
> | main ()
> | {
> | exit (42);
> |   ;
> |   return 0;
> | }
> configure:3665: g++ -c -g -O2 -fstack-protector --param=ssp-buffer-size=4 
> -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 conftest.cc >&5
> conftest.cc:9:40: error: 'void std::exit(int)' should have been declared 
> inside 'std'
>  extern "C" void std::exit (int) throw (); using std::exit;
> ^
> configure:3671: $? = 1
> configure: failed program was:
> | /* confdefs.h.  */
> | 
> | #define PACKAGE_NAME "gtkglextmm"
> | #define PACKAGE_TARNAME "gtkglextmm"
> | #define PACKAGE_VERSION "1.2.0"
> | #define PACKAGE_STRING "gtkglextmm 1.2.0"
> | #define PACKAGE_BUGREPORT "gtkglext-deve...@lists.sourceforge.net"
> | /* end confdefs.h.  */
> | extern "C" void std::exit (int) throw (); using std::exit;
> | #include 
> | int
> | main ()
> | {
> | exit (42);
> |   ;
> |   return 0;
> | }
> configure:3665: g++ -c -g -O2 -fstack-protector --param=ssp-buffer-size=4 
> -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 conftest.cc >&5
> conftest.cc:9:31: error: 'void std::exit(int)' should have been declared 
> inside 'std'
>  extern "C" void std::exit (int); using std::exit;
>^
> In file included from conftest.cc:10:0:
> /usr/include/stdlib.h:542:70: error: declaration of 'void std::exit(int) 
> throw ()' has a different exception specifier
>  extern void exit (int __status) __THROW __attribute__ ((__noreturn__));
>   ^
> conftest.cc:9:17: error: from previous declaration 'void std::exit(int)'
>  extern "C" void std::exit (int); using std::exit;
>  ^
> configure:3671: $? = 1
> configure: failed program was:
> | /* confdefs.h.  */
> | 
> | #define PACKAGE_NAME "gtkglextmm"
> | #define PACKAGE_TARNAME "gtkglextmm"
> | #define PACKAGE_VERSION "1.2.0"
> | #define PACKAGE_STRING "gtkglextmm 1.2.0"
> | #define PACKAGE_BUGREPORT "gtkglext-deve...@lists.sourceforge.net"
> | /* end confdefs.h.  */
> | extern "C" void std::exit (int); using std::exit;
> | #include 
> | int
> | main ()
> | {
> | exit (42);
> |   ;
> |   return 0;
> | }
> configure:3665: g++ -c -g -O2 -fstack-protector --param=ssp-buffer-size=4 
> -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 conftest.cc >&5
> configure:3671: $? = 0
> configure:3675: test -z 
>|| test ! -s conftest.err
> configure:3678: $? = 0
> configure:3681: test -s conftest.o
> configure:3684: $? = 0
> configure:3710: g++ -c -g -O2 -fstack-protector --param=ssp-buffer-size=4 
> -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 conftest.cc >&5
> configure:3716: $? = 0
> configure:3720: test -z 
>|| test ! -s conftest.err
> configure:3723: $? = 0
> configure:3726: test -s conftest.o
> configure:3729: $? = 0
> configure:3754: checking dependency st