Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 29 Mar 2017 21:44:03 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-toolchain@FreeBSD.org
Subject:   [Bug 214855] head -r309179 TARGET_ARCH=powerpc64 clang 3.9.0 based cross build: powerpc.powerpc64/usr/src/tmp/usr/bin/ld: BFD 2.17.50 [FreeBSD] 2007-07-03 internal error
Message-ID:  <bug-214855-29464-BwaCPXXjrq@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-214855-29464@https.bugs.freebsd.org/bugzilla/>
References:  <bug-214855-29464@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214855

--- Comment #5 from Mark Millard <markmi@dsl-only.net> ---
(In reply to Justin Hibbits from comment #4)

ld from 2.25 and from 2.27 from ports has worked fine.

But I'm not sure if by "newer" Justin was referring to
such vs. referring to potential updates to the system
2.17.* ld.

While code that handles thrown C++ exceptions fails
at run-time I'm able to use clang to buildworld and
boot and use FreeBSD for powerpc64 based on the
ports binutils (although I've not tried the new 2.28).

[I reverted to 2.27 when I found that arm64/aarch64
was broken for buildworld buildkernel (at least for
cross building from amd64). I did this before trying
powerpc64 or powerpc.]

[Unfortunately without C++ exception handling working
kyua can not be used on powerpc64. In my view that is
sufficient to say that clang is still insufficient to
be the system compiler for powerpc64 --ignoring any
system binutils or lld issues hat force port binutils
use.]

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-214855-29464-BwaCPXXjrq>