Your message dated Sun, 13 Oct 2013 21:30:41 +0200
with message-id <65798932.zz076VH5xd@sephirot>
and subject line builds ok
has caused the Debian Bug report #713456,
regarding apq-postgresql: FTBFS: cc1: error: unrecognized command line option 
'-fno-aggressive-loop-optimizations'cc1: error: unrecognized command line 
option '-fno-aggressive-loop-optimizations'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
713456: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713456
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apq-postgresql
Version: 3.2.0-2
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:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> ./scripts/build.sh
> 
> ############################
> # Building Debug Libraries #
> ############################
> Building static library
> completed 1 out of 5 (20%)...
> cc1: error: unrecognized command line option 
> '-fno-aggressive-loop-optimizations'cc1: error: unrecognized command line 
> option '-fno-aggressive-loop-optimizations'
> completed 2 out of 5 (40%)...
> 
> 
> gprbuild: *** compilation phase failed
>    compilation of notices.c failed
>    compilation of numeric.c failed
> 
> Building relocatable library
> completed 1 out of 5 (20%)...
> cc1: error: unrecognized command line option 
> '-fno-aggressive-loop-optimizations'cc1: error: unrecognized command line 
> option '-fno-aggressive-loop-optimizations'
> completed 2 out of 5 (40%)...
> 
> gprbuild: *** compilation phase failed
> 
>    compilation of numeric.c failed
>    compilation of notices.c failed
> 
> ##############################
> # Building Regular Libraries #
> ##############################
> Building static library
> completed 1 out of 5 (20%)...
> cc1: error: unrecognized command line option 
> '-fno-aggressive-loop-optimizations'cc1: error: unrecognized command line 
> option '-fno-aggressive-loop-optimizations'
> completed 2 out of 5 (40%)...
> 
> gprbuild: *** compilation phase failed
> 
>    compilation of numeric.c failed
>    compilation of notices.c failed
> 
> Building relocatable library
> completed 1 out of 5 (20%)...
> cc1: error: unrecognized command line option 
> '-fno-aggressive-loop-optimizations'cc1: error: unrecognized command line 
> option '-fno-aggressive-loop-optimizations'
> completed 2 out of 5 (40%)...
> 
> gprbuild: *** compilation phase failed
> 
>    compilation of notices.c failed
>    compilation of numeric.c failed
> 
> make[1]: Leaving directory `/«PKGBUILDDIR»'
>    dh_auto_test
>  fakeroot debian/rules binary
> dh binary
>    dh_testroot
>    dh_prep
>    debian/rules override_dh_auto_install
> make[1]: Entering directory `/«PKGBUILDDIR»'
> dh_auto_install
> make[2]: Entering directory `/«PKGBUILDDIR»'
> ./scripts/install.sh
> make[2]: Leaving directory `/«PKGBUILDDIR»'
> rm -f debian/tmp/usr/lib/apq-postgresql-debug/relocatable/libapq-postgresql.so
> chmod 644 debian/tmp/usr/lib/apq-postgresql-debug/relocatable/*
> chmod 644 debian/tmp/usr/lib/apq-postgresql-debug/static/libapq-postgresql.a
> chmod: cannot access 
> 'debian/tmp/usr/lib/apq-postgresql-debug/static/libapq-postgresql.a': No such 
> file or directory
> make[1]: *** [override_dh_auto_install] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/20/apq-postgresql_3.2.0-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.

--- End Message ---
--- Begin Message ---
Now builds ok, closing it.

David

--- End Message ---

Reply via email to