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 Millard wrote: > >>

Re: HEADS-UP: Merged llvm/clang 5.0.0 into -CURRENT (as of r321369)

2017-07-23 Thread Mark Millard
On 2017-Jul-23, at 7:44 PM, Shawn Webb wrote: > On Sun, Jul 23, 2017 at 09:16:26PM -0400, Shawn Webb wrote: >> On Sun, Jul 23, 2017 at 07:34:47PM -0400, Shawn Webb wrote: >>> On Sun, Jul 23, 2017 at 04:13:18PM -0700, Mark Millard wrote: Shawn Webb shawn.webb at hardenedbsd.org wrote on

Re: HEADS-UP: Merged llvm/clang 5.0.0 into -CURRENT (as of r321369)

2017-07-23 Thread Mark Millard
On 2017-Jul-23, at 6:16 PM, Shawn Webb wrote: > On Sun, Jul 23, 2017 at 07:34:47PM -0400, Shawn Webb wrote: >> On Sun, Jul 23, 2017 at 04:13:18PM -0700, Mark Millard wrote: >>> Shawn Webb shawn.webb at hardenedbsd.org wrote on >>> Sat Jul 22 15:33:14 UTC 2017 : >>> I haven't nailed down wh

Re: HEADS-UP: Merged llvm/clang 5.0.0 into -CURRENT (as of r321369)

2017-07-23 Thread Shawn Webb
On Sun, Jul 23, 2017 at 09:16:26PM -0400, Shawn Webb wrote: > On Sun, Jul 23, 2017 at 07:34:47PM -0400, Shawn Webb wrote: > > On Sun, Jul 23, 2017 at 04:13:18PM -0700, Mark Millard wrote: > > > Shawn Webb shawn.webb at hardenedbsd.org wrote on > > > Sat Jul 22 15:33:14 UTC 2017 : > > > > > > > I h

Re: HEADS-UP: Merged llvm/clang 5.0.0 into -CURRENT (as of r321369)

2017-07-23 Thread Shawn Webb
On Sun, Jul 23, 2017 at 07:34:47PM -0400, Shawn Webb wrote: > On Sun, Jul 23, 2017 at 04:13:18PM -0700, Mark Millard wrote: > > Shawn Webb shawn.webb at hardenedbsd.org wrote on > > Sat Jul 22 15:33:14 UTC 2017 : > > > > > I haven't nailed down whether it's SafeStack, CFI, or using lld as the > >

Re: amd64 -r321109 -> -r321371 buildworld update failed (spans clang 5 update); error: too few arguments provided to function-like macro invocation; , METAMODE and -j8 was used

2017-07-23 Thread Mark Millard
On 2017-Jul-22, at 5:09 PM, Dimitry Andric wrote: > On 23 Jul 2017, at 02:02, Mark Millard wrote: >> >> On 2017-Jul-22, at 4:50 PM, Dimitry Andric wrote: >>> On 23 Jul 2017, at 01:32, Mark Millard wrote: My first attempt to update amd64 to a clang 5 based /usr/src failed ( -r3

Re: HEADS-UP: Merged llvm/clang 5.0.0 into -CURRENT (as of r321369)

2017-07-23 Thread Shawn Webb
On Sun, Jul 23, 2017 at 04:13:18PM -0700, Mark Millard wrote: > Shawn Webb shawn.webb at hardenedbsd.org wrote on > Sat Jul 22 15:33:14 UTC 2017 : > > > I haven't nailed down whether it's SafeStack, CFI, or using lld as the > > default linker, but it looks like we in HardenedBSD are getting an > >

Re: HEADS-UP: Merged llvm/clang 5.0.0 into -CURRENT (as of r321369)

2017-07-23 Thread Mark Millard
Shawn Webb shawn.webb at hardenedbsd.org wrote on Sat Jul 22 15:33:14 UTC 2017 : > I haven't nailed down whether it's SafeStack, CFI, or using lld as the > default linker, but it looks like we in HardenedBSD are getting an > undefined symbol during buildworld. In an amd64 -> TARGET_ARCH=powerpc64

FWD: libstdc++ build failures on MIPS, PowerPC, Sparc

2017-07-23 Thread Mark Millard
[Just a forward of someone else's note about gcc 4.2.1 build problems -in -r321376 .] Ravi Pokala rpokala at mac.com wrote on Sun Jul 23 19:44:57 UTC 2017 : > I did a tinderbox build of -HEAD as of r321376; there were failures like this > (paths shortened): > > c++ -isystem ${OUTDIR}/tmp/us

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
[WITH_LLD= WITHOUT_LLDB= did a buildworld buildkernel just fine for TARGET_ARCH=powerpc64 .] On 2017-Jul-23, at 2:46 PM, Mark Millard wrote: > [Shawn Webb's logfile shows an error similar to what I > report: lldb_private::AppleObjCRuntime::GetFoundationVersion() > is a problem. But his report sh

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
[Shawn Webb's logfile shows an error similar to what I report: lldb_private::AppleObjCRuntime::GetFoundationVersion() is a problem. But his report shows other errors as well, ones that I did not get.] On 2017-Jul-23, at 1:04 PM, Mark Millard wrote: > [The lldb problem is a: > > lldb_private::Ap

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 prel

-r321371 amd64 -> powerpc (32-bit) cross build: ld: agp.kld(.text+0x2e08): R_PPC_PLTREL24 reloc against local symbol

2017-07-23 Thread Mark Millard
[Note: Due to other things going on in various cases I need to go back sometime later and extract more information after some my initial reports. Sorry. I figured that the preliminary notes were still appropriate in such cases.] This was a build using clang 5. I experiment with using clang for tar

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 Dimitry Andric
On 23 Jul 2017, at 11:17, Mark Millard wrote: > > [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.] ... > > Here is the lldb.full failure text: > > --- all_subdir_usr.bin

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 devel/powerpc6

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.