On 30 December 2017 at 00:28, Konstantin Belousov wrote:
> On Sat, Dec 30, 2017 at 07:50:19AM +, blubee blubeeme wrote:
>> Is there some way to programmatically get the CPU cache line sizes on
>> FreeBSD?
>
> There are, all of them are MD.
>
> On x86, the CPUID
On Sun, 2017-12-31 at 15:53 -0800, Oleksandr Tymoshenko wrote:
> Nathan Whitehorn (nwhiteh...@freebsd.org) wrote:
> >
> >
> >
> > On 12/31/17 14:22, Oleksandr Tymoshenko wrote:
> > >
> > > Michael Butler (i...@protected-networks.net) wrote:
> > > >
> > > > Building
Nathan Whitehorn (nwhiteh...@freebsd.org) wrote:
>
>
> On 12/31/17 14:22, Oleksandr Tymoshenko wrote:
> > Michael Butler (i...@protected-networks.net) wrote:
> >> Building /usr/obj/usr/src/amd64.amd64/sys/VM01/vt_font_default.o
> >> --- vt_termcolors.o ---
> >>
On 12/31/17 14:22, Oleksandr Tymoshenko wrote:
Michael Butler (i...@protected-networks.net) wrote:
Building /usr/obj/usr/src/amd64.amd64/sys/VM01/vt_font_default.o
--- vt_termcolors.o ---
/usr/src/sys/dev/vt/colors/vt_termcolors.c:158:55: error: too many
arguments to function call, expected
Michael Butler (i...@protected-networks.net) wrote:
> Building /usr/obj/usr/src/amd64.amd64/sys/VM01/vt_font_default.o
> --- vt_termcolors.o ---
> /usr/src/sys/dev/vt/colors/vt_termcolors.c:158:55: error: too many
> arguments to function call, expected 4, have 5
> if
On Sun, 2017-12-31 at 16:32 -0500, Michael Butler wrote:
> Building /usr/obj/usr/src/amd64.amd64/sys/VM01/vt_font_default.o
> --- vt_termcolors.o ---
> /usr/src/sys/dev/vt/colors/vt_termcolors.c:158:55: error: too many
> arguments to function call, expected 4, have 5
> if
Building /usr/obj/usr/src/amd64.amd64/sys/VM01/vt_font_default.o
--- vt_termcolors.o ---
/usr/src/sys/dev/vt/colors/vt_termcolors.c:158:55: error: too many
arguments to function call, expected 4, have 5
if (vt_parse_rgb_triplet(rgb, strlen(rgb), ,
, ) == 0) {
On 12/31/17 12:17, Colin Percival wrote:
> Oops! It never occurred to me that I had to worry about userland programs
> defining _KERNEL and then including kernel headers... I think I know how to
> fix this, just testing now.
Should be fixed now.
--
Colin Percival
Security Officer Emeritus,
On 12/31/17 09:35, Herbert J. Skuhra wrote:
> On Sun, 31 Dec 2017 15:19:21 +0100,
> Michael Butler wrote:
>>
>> ===> lib/libprocstat (obj,all,install)
>> Building /usr/obj/usr/src/amd64.amd64/lib/libprocstat/zfs/zfs.o
>> In file included from
Shawn Webb writes:
> > > > It looks like evdev support in the kernel is broken.
> > > > sys/dev/kbdmux/kbdmux.c contains various unresolved symbols to
> > > > different evdev-related symbols.
> > > >
> > > > I have the following options in my kernel config:
> > > >
> > > > options
On Sun, 31 Dec 2017 15:19:21 +0100,
Michael Butler wrote:
>
> An include file change? I couldn't see the cause :-(
>
> The last successful build I have is at SVN r327392.
>
> ===> lib/libprocstat (obj,all,install)
> Building
On Sun, 2017-12-31 at 09:36 +0100, Matthias Apitz wrote:
> El día sábado, diciembre 30, 2017 a las 10:48:19p. m. +0100, Matthias Apitz
> escribió:
>
> >
> > El día sábado, diciembre 30, 2017 a las 11:11:54p. m. +0200, Konstantin
> > Belousov escribió:
> >
> > >
> > > >
> > > > >
> > > > >
An include file change? I couldn't see the cause :-(
The last successful build I have is at SVN r327392.
===> lib/libprocstat (obj,all,install)
Building /usr/obj/usr/src/amd64.amd64/lib/libprocstat/zfs/zfs.o
In file included from /usr/src/lib/libprocstat/zfs.c:41:
El día sábado, diciembre 30, 2017 a las 10:48:19p. m. +0100, Matthias Apitz
escribió:
> El día sábado, diciembre 30, 2017 a las 11:11:54p. m. +0200, Konstantin
> Belousov escribió:
>
> > > > > static inline u_char
> > > > > bcd2bin(int bcd)
> > > > > {
> > > > >
> > > > > KASSERT(bcd
14 matches
Mail list logo