Date: Thu, 21 Mar 2024 04:39:36 +0000 From: Alexey Dokuchaev <danfe@freebsd.org> To: Ryan Steinmetz <zi@freebsd.org> Cc: ports-committers@freebsd.org, dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org Subject: Re: git: e42136cbdecd - main - databases/keydb: Add NOT_FOR_ARCHS for i386 due to build failure Message-ID: <Zfu6CC_lYWU_oa8-@FreeBSD.org> In-Reply-To: <202403201455.42KEtoua068470@gitrepo.freebsd.org> References: <202403201455.42KEtoua068470@gitrepo.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 20, 2024 at 02:55:50PM +0000, Ryan Steinmetz wrote: > commit e42136cbdecd7bb6a415e064a4b5803075bee1f4 > > databases/keydb: Add NOT_FOR_ARCHS for i386 due to build failure > > @@ -10,6 +10,9 @@ WWW= https://docs.keydb.dev/ > LICENSE= BSD3CLAUSE > LICENSE_FILE= ${WRKSRC}/COPYING > > +NOT_FOR_ARCHS= i386 > +NOT_FOR_ARCHS_REASON= build failure NOT_FOR_ARCHS is for the cases when something is inherently unportable and thus cannot work on some architectures; generic build failures are typically annotated as BROKEN_$arch, using an excerpt of the error message as its value, e.g. for this port: BROKEN_i386= assertion failed: static_assert(sizeof(long) == sizeof(long long),"") Even if upstream deliberately does this to prevent building on 32 bits, "build failure" as NFA_REASON is too generic and thus not very helpful. ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Zfu6CC_lYWU_oa8->