For those running FreeBSD head, the ABI was majorly changed in r318736
for 64-bit inodes. This change was *backwards compatible* but not
*forward compatible*. This is normal and expected.
For Pkg users:
You are advised to upgrade your system past r318736 soon or avoid using
official packages u
Hi!
> For those running FreeBSD head, the ABI was majorly changed in r318736
> for 64-bit inodes. This change was *backwards compatible* but not
> *forward compatible*. This is normal and expected.
Is any fall-out from this change already handled or is it wise
to wait a few more days ?
--
p..
On 26 May 2017 at 12:18, Kurt Jaeger wrote:
> Hi!
>
>> For those running FreeBSD head, the ABI was majorly changed in r318736
>> for 64-bit inodes. This change was *backwards compatible* but not
>> *forward compatible*. This is normal and expected.
>
> Is any fall-out from this change already ha
On 5/26/2017 8:20 AM, Bryan Drewery wrote:
> For those running FreeBSD head, the ABI was majorly changed in r318736
> for 64-bit inodes. This change was *backwards compatible* but not
> *forward compatible*. This is normal and expected.
>
> For Pkg users:
>
> You are advised to upgrade your sys
Is there any hope we will get src.conf flags to specify which clang x-build
tools world builds? For example build for i386 but not ARM.?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe
To briefly summarize the previous post related to perf. degradation when
running a
recent kernel...
- kernel build running 1yr old kernel took 100minutes
- same kernel build running recent kernel 148minutes
(ie. Almost a 50% degradation.)
As noted in the last post, I got rid of most of the
On Fri, May 26, 2017 at 09:57:16PM +, Rick Macklem wrote:
> I have now found I can get rid of almost all of the degradation by building
> the
> recent kernel with
> options SCHED_4BSD
> instead of
> options SCHED_ULE
>
> The 1yr old kernel was built with SCHED_ULE, so the degradation is some