Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 12 Aug 2023 20:45:53 +0200
From:      Robert Clausecker <fuz@fuz.su>
To:        "Sergey A. Osokin" <osa@freebsd.org>
Cc:        Alexey Dokuchaev <danfe@freebsd.org>, ports-committers@freebsd.org, dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org
Subject:   Re: git: a297d3477dca - main - devel/libwasmtime: mark build failed on i386 (+)
Message-ID:  <ZNfTYcjyHifEYEoq@fuz.su>
In-Reply-To: <ZNfSx7o8uou7cxF6@FreeBSD.org>
References:  <202308112058.37BKwAxr071903@gitrepo.freebsd.org> <ZNcHKq8lu1gwb4J0@FreeBSD.org> <ZNfSx7o8uou7cxF6@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi Sergey,

Am Sat, Aug 12, 2023 at 06:43:19PM +0000 schrieb Sergey A. Osokin:
> On Sat, Aug 12, 2023 at 04:14:34AM +0000, Alexey Dokuchaev wrote:
> > On Fri, Aug 11, 2023 at 08:58:10PM +0000, Sergey A. Osokin wrote:
> > > commit a297d3477dca8f76ef3461b6b0c760d05be3cddd
> > > 
> > >   devel/libwasmtime: mark build failed on i386 (+)
> > > ...
> > > -USES=	cargo
> > > +NOT_FOR_ARCHS=	i386
> > > +NOT_FOR_ARCHS_REASON=	build currently failing
> > 
> > Why not simply BROKEN_i386?
> 
> Not sure how many unsupported archs there, will see.

If the port is broken for multiple architectures, add one BROKEN_...
line for each architecture on which the port is broken.  We have
NOT_FOR_ARCHS distinct from BROKEN so it's easy to discover broken
ports and fix them.  Please don't mix these two up.

> -- 
> Sergey A. Osokin

Yours,
Robert Clausecker

-- 
()  ascii ribbon campaign - for an 8-bit clean world 
/\  - against html email  - against proprietary attachments



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZNfTYcjyHifEYEoq>