Re: -r321371 amd64 -> powerpc64 cross build: lldb.full link fails with: c++: error: linker command failed with exit code 1, -B/usr/local/powerpc64-freebsd/bin/ in use

2017-07-26 Thread Mark Millard
On 2017-Jul-24, at 7:28 AM, Warner Losh wrote: >> On Mon, Jul 24, 2017 at 1:33 AM, Mark Millard wrote: >> [I forgot that linking lldb historically failed on armv6 >> (cortex-a7) based on the historical system binutils.] >> >> On 2017-Jul-23, at 8:51 PM, Mark Millard wrote: >> >> > [Using

Re: -r321371 amd64 -> powerpc64 cross build: lldb.full link fails with: c++: error: linker command failed with exit code 1, -B/usr/local/powerpc64-freebsd/bin/ in use

2017-07-24 Thread Warner Losh
On Mon, Jul 24, 2017 at 1:33 AM, Mark Millard wrote: > [I forgot that linking lldb historically failed on armv6 > (cortex-a7) based on the historical system binutils.] > > On 2017-Jul-23, at 8:51 PM, Mark Millard wrote: > > > [Using WITH_LLDB= had no

Re: -r321371 amd64 -> powerpc64 cross build: lldb.full link fails with: c++: error: linker command failed with exit code 1, -B/usr/local/powerpc64-freebsd/bin/ in use

2017-07-24 Thread Mark Millard
[I forgot that linking lldb historically failed on armv6 (cortex-a7) based on the historical system binutils.] On 2017-Jul-23, at 8:51 PM, Mark Millard wrote: > [Using WITH_LLDB= had no problem for amd64 -> TARGET_ARCH=aarch64 > buildworld buildkernel .] > > On

Re: -r321371 amd64 -> powerpc64 cross build: lldb.full link fails with: c++: error: linker command failed with exit code 1, -B/usr/local/powerpc64-freebsd/bin/ in use

2017-07-23 Thread Mark Millard
[Using WITH_LLDB= had no problem for amd64 -> TARGET_ARCH=aarch64 buildworld buildkernel .] On 2017-Jul-23, at 3:44 PM, Mark Millard wrote: > [WITH_LLD= WITHOUT_LLDB= did a buildworld buildkernel > just fine for TARGET_ARCH=powerpc64 .] > > On 2017-Jul-23, at 2:46 PM, Mark

Re: -r321371 amd64 -> powerpc64 cross build: lldb.full link fails with: c++: error: linker command failed with exit code 1, -B/usr/local/powerpc64-freebsd/bin/ in use

2017-07-23 Thread Mark Millard
[The lldb problem is a: lldb_private::AppleObjCRuntime::GetFoundationVersion() reference via Cocoa.o in liblldb.a . See below. Sorry that sometimes I'm having to go back and later find and report more details because of other things going on here. But this likely will continue for some of my

Re: -r321371 amd64 -> powerpc64 cross build: lldb.full link fails with: c++: error: linker command failed with exit code 1, -B/usr/local/powerpc64-freebsd/bin/ in use

2017-07-23 Thread Mark Millard
[Linking lldb.full via 2.28 of /usr/local/powerpc64-freebsd/bin/ld also fails with "exit code 1" (using WIHTOUT_LLD so it gets that far). I'll continue via WITHOUT_LLDB.] On 2017-Jul-23, at 12:42 AM, Mark Millard wrote: > On 2017-Jul-23, at 12:34 AM, Mark Millard wrote: > >> The

Re: -r321371 amd64 -> powerpc64 cross build: lldb.full link fails with: c++: error: linker command failed with exit code 1, -B/usr/local/powerpc64-freebsd/bin/ in use

2017-07-23 Thread Mark Millard
On 2017-Jul-23, at 12:34 AM, Mark Millard wrote: > The devel/powerpc64-binutils is failing to link lldb.full for > the clang/llvm 5 based context. (I historically use WITH_LLD > when targeting powerpc64 but do not use lldb since it did not > work overall.) I will simply change to WITHOUT_LLD for

-r321371 amd64 -> powerpc64 cross build: lldb.full link fails with: c++: error: linker command failed with exit code 1, -B/usr/local/powerpc64-freebsd/bin/ in use

2017-07-23 Thread Mark Millard
The devel/powerpc64-binutils is failing to link lldb.full for the clang/llvm 5 based context. (I historically use WITH_LLD when targeting powerpc64 but do not use lldb since it did not work overall.) I will simply change to WITHOUT_LLD for now. I show the build context before the full error text.