On 2015-06-01 9:24 AM, Matthias Klose wrote:
On 05/30/2015 10:59 PM, John David Anglin wrote:
On 2015-05-29, at 5:18 PM, Matthias Klose wrote:
Anyway, please check if this is the real cause. attaching a hack which should
work around that.
The hack didn't fix build. Here is log:
http://buildd.debian-ports.org/status/fetch.php?pkg=gcc-5&arch=hppa&ver=5.1.1-9&stamp=1433017924
yep, here is what I'm checking in. should be good enough for hppa64.
Index: b/src/configure.ac
===================================================================
--- a/src/configure.ac
+++ b/src/configure.ac
@@ -147,6 +147,11 @@ libgcj="target-libffi \
target-zlib \
target-libjava"
+case x"${target}" in
Do we need the x?
+ hppa64-*linux*) ;;
+ *) target_libiberty="target-libiberty";;
+esac
+
# these libraries are built for the target environment, and are built after
# the host libraries and the host tools (which may be a cross compiler)
# Note that libiberty is not a target library.
It seems libiberty was explicitly omitted as a target library.
@@ -170,6 +175,7 @@ target_libraries="target-libgcc \
${libgcj} \
target-libobjc \
target-libada \
+ ${target_libiberty} \
target-libgo"
# these tools are built using the target libraries, and are intended to
--
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-smtp1125c095a9cf2ffb4805fe297...@phx.gbl
