Your message dated Mon, 02 Jul 2012 03:10:12 +0200
with message-id <[email protected]>
and subject line Fix with version 3.1
has caused the Debian Bug report #678761,
regarding dragonegg: FTBFS: g++-4.6: error: directory": No such file or
directory
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 [email protected]
immediately.)
--
678761: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678761
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: dragonegg
Version: 3.0-3.2
Severity: serious
Tags: wheezy sid
User: [email protected]
Usertags: qa-ftbfs-20120624 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»'
> Compiling utils/TargetInfo.cpp
> g++-4.6 -c -DTARGET_TRIPLE=\"x86_64-linux-gnu\" \
> -I/usr/lib/llvm-3.0/include -DNDEBUG -D_GNU_SOURCE
> -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -MD -MP
> -DIN_GCC -DREVISION=\"Unversioned directory\" -DGCC_MAJOR=4 -DGCC_MINOR=6
> -DGCC_MICRO=0 -I/«PKGBUILDDIR»/include
> -I/usr/lib/gcc/x86_64-linux-gnu/4.6/plugin/include -Wall -Wextra
> -fvisibility=hidden -I/usr/lib/llvm-3.0/include -DNDEBUG -D_GNU_SOURCE
> -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -g -O2
> -fomit-frame-pointer -fno-exceptions -fPIC -Woverloaded-virtual -Wcast-qual
> /«PKGBUILDDIR»/utils/TargetInfo.cpp
> g++-4.6: error: directory": No such file or directory
> make[1]: *** [TargetInfo.o] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2012/06/24/dragonegg_3.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.
--- End Message ---
--- Begin Message ---
fixed 678761 3.1-1
thanks
--- End Message ---