After ino64 update: devel/libunwind failure: cannot preempt symbol '_Ux86_64_local_addr_space' defined

2017-05-29 Thread O. Hartmann
After updating several boxes running CURRENT after introduction of ino64, I have one box which persitently rejects compiling and installing devel/libunwind, as you can finde below. The box in question is running FreeBSD 12.0-CURRENT #22 r319083: Sun May 28 21:18:52 CEST 2017 amd64, WITH_LLD_IS_LD

Re: NFS client perf. degradation when SCHED_ULE is used (was when SMP enabled)

2017-05-29 Thread Andriy Gapon
On 28/05/2017 01:20, Rick Macklem wrote: > - with the "obvious change" mentioned in r312426's commit message, using >(flags & SW_TYPE_MASK) == SWT_RELINQUISH instead of (flag & SWT_RELINQUISH) >121minutes Rick, can I see how exactly

ino64 status update and upgrade caution

2017-05-29 Thread Ed Maste
The ino64 project was committed to src last week[1][2] with UPDATING notes added shortly thereafter [3][4][5]. As some people have been tripped up by the ino64 change I want to emphasize again that the upgrade procedure described in UPDATING should be followed exactly. The reboot after installing

Re: After ino64 update: devel/libunwind failure: cannot preempt symbol '_Ux86_64_local_addr_space' defined

2017-05-29 Thread Ed Maste
On 29 May 2017 at 04:59, O. Hartmann wrote: > After updating several boxes running CURRENT after introduction of ino64, I > have one box which persitently rejects compiling and installing > devel/libunwind, as you can finde below. > > The box in question is running FreeBSD 12.0-CURRENT #22 r31908

Xorg error 'alphasort'

2017-05-29 Thread Jeffrey Bouquet
First try, did not build, to try to fix, Xorg, took the easy way out and restored the /usr/local/bin/Xorg that was working two days ago from backup. Xorg.log.0 says it is devd??? ... error in Subject is only from memory. ...

side-effects from mesa-libs and ino64 updates ...?

2017-05-29 Thread Kevin Casey
I would appreciate observations about two difficulties that have surfaced for me since the mesa-libs and ino64 updates. Likely these are pilot errors but I've not been able to identify the causes. Here's the environment ... FreeBSD silver 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r318232: Fri May 1