<html><head></head><body>Apparently, installing latest update of Slackware-current should fix that problem.<br><br>Changelog says you need tu run autoreconf -vif for exactly that problem, with automake-1.16.5<br><br> - Yth.<br><br><div class="gmail_quote">Le 11 octobre 2021 04:06:51 UTC, David Chmelik <dchmelik@gmail.com> a écrit :<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre dir="auto" class="k9mail">People were able to get zfs-on-linux (now actually openzfs) working on <br>Slackware64-current by just changing the SlackBuild version number. <br>People should be using 2.1.1 now and in SBo-git it should be updated to <br>reflect that. However with the recent Slackware64-current python3 <br>upgrade, zfs-on-linux will no longer build. Its configure script is <br>broken and detects python 3.10.0 as 3.1 and says it's too old, so won't <br>continue. What can be done about this meantime so people can continue <br>to use zfs-on-linux with newer kernels on Slackware64-current before <br>Slackware 15?<hr>SlackBuilds-users mailing list<br>SlackBuilds-users@slackbuilds.org<br><a href="https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users">https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a><br>Archives - <a href="https://lists.slackbuilds.org/pipermail/slackbuilds-users/">https://lists.slackbuilds.org/pipermail/slackbuilds-users/</a><br>FAQ - <a href="https://slackbuilds.org/faq/">https://slackbuilds.org/faq/</a><br><br></pre></blockquote></div><div style='white-space: pre-wrap'><div class='k9mail-signature'>-- <br></div></div></body></html>