Bug#847478: FTBFS: needs to Build-Depends on gperf
control: tag -1 + moreinfo
On 2016-12-08 16:42, Ximin Luo wrote:
> Package: glibc
> Version: 2.24-7
> Severity: serious
> Tags: patch
> Justification: fails to build from source (but built successfully in the past)
>
> Dear Maintainer,
>
> whilst trying to build glibc:
>
> /usr/bin/install -c -m 644 /tmp/debrepro.uGH5xEsmL1/build/source/build-tree/amd64-libc/gnu/lib-names-64.h /tmp/debrepro.uGH5xEsmL1/build/source/debian/tmp-libc/usr/include/gnu/lib-names-64.h
> /usr/bin/install -c -m 644 /tmp/debrepro.uGH5xEsmL1/build/source/build-tree/amd64-libc/libBrokenLocale.map /tmp/debrepro.uGH5xEsmL1/build/source/debian/tmp-libc/usr/lib/x86_64-linux-gnu/libBrokenLocale_pic.map
> cd programs \
> && gperf -acCgopt -k1,2,5,9,$ -L ANSI-C -N charmap_hash charmap-kw.gperf > charmap-kw.h.new
> /bin/bash: line 1: gperf: command not found
> Makefile:66: recipe for target 'programs/charmap-kw.h' failed
> make[3]: *** [programs/charmap-kw.h] Error 127
> make[3]: Leaving directory '/tmp/debrepro.uGH5xEsmL1/build/source/locale'
> Makefile:230: recipe for target 'locale/subdir_install' failed
> make[2]: *** [locale/subdir_install] Error 2
> make[2]: Leaving directory '/tmp/debrepro.uGH5xEsmL1/build/source'
> Makefile:12: recipe for target 'install' failed
> make[1]: *** [install] Error 2
> make[1]: Leaving directory '/tmp/debrepro.uGH5xEsmL1/build/source/build-tree/amd64-libc'
> debian/rules.d/build.mk:162: recipe for target '/tmp/debrepro.uGH5xEsmL1/build/source/stamp-dir/install_libc' failed
> make: *** [/tmp/debrepro.uGH5xEsmL1/build/source/stamp-dir/install_libc] Error 2
> dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
>
> I: artifacts left in /tmp/debrepro.uGH5xEsmL1
>
> Probably this just needs a Build-Depends: gperf, I am trying the build again now.
Strange, I am not able to reproduce the problem, the package built fine
here. Also it built fine on the build daemons for quite some time and
there hasn't been any recent change besides hurd one.
Are you doing something special to trigger this bug? Do you have the
build log?
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://www.aurel32.net
Reply to: