Bug#786692: gcc-5: FTBFS on hppa: configure error for configure-target-libiberty building hppa64
On 05/24/2015 03:34 PM, John David Anglin wrote:
> Source: gcc-5
> Version: 5.1.1-6
> Severity: normal
>
> A since 5.1.1-6, gcc-5 no longer builds on hppa:
>
> checking size of long... 0
> checking for long long... no
> checking for a 64-bit type... unsigned long
> checking for intptr_t... no
> checking for uintptr_t... no
> checking for ssize_t... no
> checking for pid_t... no
> configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES.
> make[3]: *** [configure-target-libiberty] Error 1
> checking for library containing strerror... Makefile:11736: recipe for target 'configure-target-libiberty' failed
> make[3]: Leaving directory '/«PKGBUILDDIR»/build-hppa64'
> make[2]: *** [all] Error 2
> make[1]: *** [stamps/05-build-hppa64-stamp] Error 2
> Makefile:859: recipe for target 'all' failed
> make[2]: Leaving directory '/«PKGBUILDDIR»/build-hppa64'
> debian/rules2:1318: recipe for target 'stamps/05-build-hppa64-stamp' failed
> make[1]: Leaving directory '/«PKGBUILDDIR»'
> make: *** [stamps/05-build-hppa64-stamp] Error 2
> debian/rules:60: recipe for target 'stamps/05-build-hppa64-stamp' failed
> dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
>
> Full buildd log is here:
> http://buildd.debian-ports.org/status/fetch.php?pkg=gcc-5&arch=hppa&ver=5.1.1-6&stamp=1432360049
>
> I tried adding --disable-libiberty to hppa64 configure command. However,
> this resulted in following error:
>
> checking whether /«PKGBUILDDIR»/build/gcc/xgcc -B/«PKGBUILDDIR»/build/gcc/ supports -Wstrict-prototypes... checking for stdint.h... libtool: link: /«PKGBUILDDIR»/build/gcc/xgcc -B/«PKGBUILDDIR»/build/gcc/ -shared -fPIC -DPIC .libs/lto-plugin.o -static-libgcc ../libiberty/libiberty.a -static-libstdc++ -static-libgcc -Wl,-soname -Wl,liblto_plugin.so.0 -o .libs/liblto_plugin.so.0.0.0
> xgcc: error: ../libiberty/libiberty.a: No such file or directory
> make[5]: *** [liblto_plugin.la] Error 1
> yes
> Makefile:351: recipe for target 'liblto_plugin.la' failed
> make[5]: Leaving directory '/«PKGBUILDDIR»/build-hppa64/lto-plugin'
> make[4]: *** [all] Error 2
> Makefile:264: recipe for target 'all' failed
> make[4]: Leaving directory '/«PKGBUILDDIR»/build-hppa64/lto-plugin'
> make[3]: *** [all-lto-plugin] Error 2
> make[3]: *** Waiting for unfinished jobs....
> Makefile:8664: recipe for target 'all-lto-plugin' failed
>
> Full log for this build is here:
> http://buildd.debian-ports.org/status/fetch.php?pkg=gcc-5&arch=hppa&ver=5.1.1-7&stamp=1432446476
>
> It is a bit of a puzzle why lto plugin support needs a target version of libiberty.
I don't think I have any packaging changes which could lead to this.
Looking at the build log, I see the CC is overridden in the build target,
can you check if removing the
CC="$(CC_for_hppa64_cross)"
line helps? fixing this in the VCS, but I don't see how this could be related.
as a last resort, you could configure the hppa64 build with --disable-lto.
Matthias
Reply to: