From owner-freebsd-current@freebsd.org Mon Mar 6 17:18:32 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 730E7CFBA6C for ; Mon, 6 Mar 2017 17:18:32 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.not-for.work (onlyone.not-for.work [148.251.9.81]) by mx1.freebsd.org (Postfix) with ESMTP id 3FE851099; Mon, 6 Mar 2017 17:18:32 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from [192.168.17.133] (unknown [89.113.128.32]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.not-for.work (Postfix) with ESMTPSA id 563DF897; Mon, 6 Mar 2017 20:18:30 +0300 (MSK) Reply-To: lev@FreeBSD.org Subject: Re: Strange kernel build breakage (after r314283?) References: <0b702c55-aa92-193f-77e1-c5c8aa1a668f@FreeBSD.org> To: FreeBSD CURRENT Cc: imp@FreeBSD.org From: Lev Serebryakov Organization: FreeBSD Message-ID: <12f82f8b-658e-23e0-c017-c917dd8cd638@FreeBSD.org> Date: Mon, 6 Mar 2017 20:18:28 +0300 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1 MIME-Version: 1.0 In-Reply-To: <0b702c55-aa92-193f-77e1-c5c8aa1a668f@FreeBSD.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Mar 2017 17:18:32 -0000 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