Date: Fri, 1 Jul 2022 11:40:51 +0200 From: Mateusz Piotrowski <0mp@FreeBSD.org> To: ports-committers@FreeBSD.org, dev-commits-ports-all@FreeBSD.org, dev-commits-ports-main@FreeBSD.org Subject: Re: git: b5097ef59669 - main - net-im/libsignal-client: Mark as broken on aarch64 Message-ID: <1c1a11ff-1cb3-d010-fb51-a0daef4d95fe@FreeBSD.org> In-Reply-To: <015699b6-4d48-2372-c0ef-902c7460a847@FreeBSD.org> References: <202207010844.2618i3BG054638@gitrepo.freebsd.org> <015699b6-4d48-2372-c0ef-902c7460a847@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 01/07/2022 11:36, Mateusz Piotrowski wrote: > On 01/07/2022 10:44, Mateusz Piotrowski wrote: >> URL: https://cgit.FreeBSD.org/ports/commit/?id=b5097ef59669c6c54c180cb20d1492b46805711e >> +BROKEN_aarch64= fails to compile: could not compile `polyval`: the feature named `crypto` >> is not valid for this target > > Hmmm, does it look like it could be fixed with RUSTC_BOOTSTRAP? > > +MAKE_ENV+= RUSTC_BOOTSTRAP=aes,polyval Nevermind, it's RUSTC_BOOTSTRAP is included in this port's MAKE_ENV. I saw https://cgit.FreeBSD.org/ports/commit/?id=ac5e87b9286eb44d8ef338f3a9cc6ae335ec8eaa and was hoping that this could be a fix for libsignal-client as well.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1c1a11ff-1cb3-d010-fb51-a0daef4d95fe>