Hi Nilesh,
so 16. 10. 2021 v 9:09 odesílatel Nilesh Patra <
[email protected]> napsal:
I see that isal package is limited to amd64, arm64 and kfreebsd-amd64.
Is there a particular reason for this? -- Is it possible to extend support
to other archs?
When I packed libisal, only "customer" was liberasurecode. Liberasurecode supports many backends and supports all archs. And because libisal is
highly optimized for ARM and amd64, I built it only for these archs. Other platforms are supported, but not optimized. liberasurecode directly should perform better.
Actually, a -med team package fastp has started to depend on libisal-dev
And because there is other "customer", I will try to build it for all
archs.
Thanks.
--
Best regards
Ondřej Nový
<div dir="ltr"><div>Hi Nilesh,</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">so 16. 10. 2021 v 9:09 odesílatel Nilesh Patra <<a href="mailto:
[email protected]">
[email protected]</a>> napsal:</div><blockquote
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
I see that isal package is limited to amd64, arm64 and kfreebsd-amd64.<br>
Is there a particular reason for this? -- Is it possible to extend support to other archs?<br></blockquote><div><br></div><div>When I packed libisal, only "customer" was liberasurecode. Liberasurecode supports many backends and supports all
archs. And because libisal is highly optimized for ARM and amd64, I built it only for these archs. Other platforms are supported, but not optimized. liberasurecode directly should perform better.</div><div><br></div><blockquote class="gmail_quote" style="
margin:0px 0px 0px 0.8ex;border-left:1