Bug#792052: marked as done (gcc-python-plugin: FTBFS: python3-dbg: not found)
Your message dated Sat, 11 Jul 2015 18:54:33 +0200
with message-id <55A14A49.6020407@debian.org>
and subject line Re: Bug#792052: gcc-python-plugin: FTBFS: python3-dbg: not found
has caused the Debian Bug report #792052,
regarding gcc-python-plugin: FTBFS: python3-dbg: not found
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 owner@bugs.debian.org
immediately.)
--
792052: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792052
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-python-plugin
Version: 0.14-1
Severity: serious
Justification: fails to build from source
Builds of gcc-python-plugin in minimal environments (notably, on the
autobuilders) have been failing:
make[1]: Entering directory '/«PKGBUILDDIR»/build-python3-dbg'
Makefile:193: warning: overriding recipe for target 'autogenerated-casts.c'
Makefile:190: warning: ignoring old recipe for target 'autogenerated-casts.c'
python3-dbg generate-config-h.py -o autogenerated-config.h --gcc="gcc-5" --plugindir="/usr/lib/gcc/aarch64-linux-gnu/5/plugin"
/bin/sh: 1: python3-dbg: not found
make[1]: *** [autogenerated-config.h] Error 127
Makefile:177: recipe for target 'autogenerated-config.h' failed
make[1]: Leaving directory '/«PKGBUILDDIR»/build-python3-dbg'
make: *** [build-stamp-python3-dbg] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
Please declare a build dependency on python3-dbg.
Thanks!
--- End Message ---
--- Begin Message ---
Version: 0.14-2
On 07/10/2015 07:20 PM, Aaron M. Ucko wrote:
> Please declare a build dependency on python3-dbg.
--- End Message ---
Reply to: