On 2015-05-29 2:25 PM, Matthias Klose wrote:
I don't think I have any packaging changes which could lead to this.
Okay. I didn't see anything in changelog entries.
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.
Yes, CC_for_hppa64_cross is not defined. Should CC be set or just
removed? Looking down
at the neon hunk below, it might have same problem.
as a last resort, you could configure the hppa64 build with --disable-lto.
I did try this and various other permutations. In some cases, the build
got to the CC_for_hppa64_cross
hunk but always something wanted target libiberty. I've wondered if the
latter hunk is needed.
I need to look at the buildd results carefully. I wasn't able to
duplicate the issue with my own cross although
I didn't try with gcc-5.
Dave
--
John David Anglin dave.ang...@bell.net
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/blu436-smtp230f55b10e8532c1dbfd5c397...@phx.gbl
