Date: Tue, 7 Mar 2017 09:13:58 -0800 From: Kevin Oberman <rkoberman@gmail.com> To: Lev Serebryakov <lev@freebsd.org> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org>, imp@freebsd.org Subject: Re: Strange kernel build breakage (after r314283?) Message-ID: <CAN6yY1uJWJ-U_9um0JnB_P3dnBpzUbigSx02PyDGG0_Yd%2BpyVg@mail.gmail.com> In-Reply-To: <12f82f8b-658e-23e0-c017-c917dd8cd638@FreeBSD.org> References: <0b702c55-aa92-193f-77e1-c5c8aa1a668f@FreeBSD.org> <12f82f8b-658e-23e0-c017-c917dd8cd638@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Mar 6, 2017 at 9:18 AM, Lev Serebryakov <lev@freebsd.org> wrote: > On 06.03.2017 20:10, Lev Serebryakov wrote: > > > I've got this error when tried to update my -CURRENT VM to r314772: > > > > /data/src/sys/cam/cam_xpt.c:84:1: error: static_assert failed > > "XPT_PRINT_LEN is too large" > > _Static_assert(XPT_PRINT_LEN <= XPT_PRINT_MAXLEN, "XPT_PRINT_LEN is too > > large"); > > ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > I didn't define any XPT_xxxx macro by hands, but I have > > > > options PRINTF_BUFR_SIZE=1024 > > > > in my kernel config. > Yep, removing this option helps, but it is surprising and not obvious > at all! > > -- > // Lev Serebryakov > If my memory is good (and it may not be), this option was recommended to prevent garbled syslog and console entries, but that was back in v8 days, long, long ago. I have not had his problem for a long time and I think that the option is no longer required and even they, 1024 was a LOT bigger than was recommended at the time. 128 or 256 seems tike the value recommended. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1uJWJ-U_9um0JnB_P3dnBpzUbigSx02PyDGG0_Yd%2BpyVg>