* David Chmelik wrote:
> People were able to get zfs-on-linux (now actually openzfs) working
> on Slackware64-current by just changing the SlackBuild version
> number. People should be using 2.1.1 now and in SBo-git it should
> be updated to reflect
people should be careful jumping on the
Apparently, installing latest update of Slackware-current should fix that
problem.
Changelog says you need tu run autoreconf -vif for exactly that problem, with
automake-1.16.5
- Yth.
Le 11 octobre 2021 04:06:51 UTC, David Chmelik a écrit :
>People were able to get zfs-on-linux (now
People were able to get zfs-on-linux (now actually openzfs) working on
Slackware64-current by just changing the SlackBuild version number.
People should be using 2.1.1 now and in SBo-git it should be updated to
reflect that. However with the recent Slackware64-current python3
upgrade,