Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 9 Jan 2020 12:02:31 -0500
From:      Ryan Moeller <ryan@ixsystems.com>
To:        freebsd-fs@freebsd.org
Cc:        kmoore@freebsd.org
Subject:   Fwd: ZoF packages & testing
Message-ID:  <CAGuotKCmyXUHh8PF4vZGKkJ-kJ1xOWLnrW=FoXrwrrpHdncRjQ@mail.gmail.com>
In-Reply-To: <CAGuotKD4r-2uAwxtirn_htG-90Es5Qo4nV86=WUzZcVYNp0tZA@mail.gmail.com>
References:  <4bb5141f-2a9c-43e0-a92a-86cfe0535bcf@www.fastmail.com> <CAGuotKD4r-2uAwxtirn_htG-90Es5Qo4nV86=WUzZcVYNp0tZA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 9, 2020 at 10:13 AM Dave Cottlehuber <dch@skunkwerks.at> wrote:
>
> Hi,
>
> I wanted to check a couple of issues I have with zfs, by using the new
> OpenZFS upstream ports, listed in:
>
> https://github.com/zfsonfreebsd/ZoF
>
> Are the OpenZFS ports/pkg going to be updated regularly or should I stick
> with source builds? pkg.freebsd.org has nothing and poudriere fails:

I will be having the port updated to the latest code today. It has
been parked on a stable git branch
over the past few months while refactoring for upstreaming occurred.
Meanwhile there have been
a number of breaking changes in the FreeBSD kernel and we have not
been the best about backporting
our fixes to the ports branch. Now the upstreaming churn has settled
down and we're ready to get the latest
code out there for testing.

>
> [00:00:09] [02] [00:00:00] Building sysutils/openzfs-kmod | openzfs-kmod-2019101600
> [00:00:16] [02] [00:00:07] Finished sysutils/openzfs-kmod | openzfs-kmod-2019101600: Failed: build
> [00:00:16] [02] [00:00:07] Skipping sysutils/openzfs | openzfs-2019101600: Dependent port sysutils/openzfs-kmod | openzfs-kmod-2019101600 failed
>
> ...
>
> In file included from /tmp/usr/ports/sysutils/openzfs-kmod/work/ZoF-d4169da/module/lua/lapi.c:12:
> In file included from /tmp/usr/ports/sysutils/openzfs-kmod/work/ZoF-d4169da/include/sys/lua/lua.h:13:
> In file included from /tmp/usr/ports/sysutils/openzfs-kmod/work/ZoF-d4169da/include/sys/zfs_context.h:45:
> In file included from /tmp/usr/ports/sysutils/openzfs-kmod/work/ZoF-d4169da/include/os/freebsd/spl/sys/kobj.h:41:
> /tmp/usr/ports/sysutils/openzfs-kmod/work/ZoF-d4169da/include/os/freebsd/spl/sys/vnode.h:225:24: error: too many arguments to function call, expected single argument 'vp', have 2 arguments
>                 VOP_UNLOCK(nd.ni_vp, 0);
>                 ~~~~~~~~~~           ^
> ./vnode_if.h:892:1: note: 'VOP_UNLOCK' declared here
> static __inline int VOP_UNLOCK(
> ^
> In file included from /tmp/usr/ports/sysutils/openzfs-kmod/work/ZoF-d4169da/module/lua/lapi.c:12:
> In file included from /tmp/usr/ports/sysutils/openzfs-kmod/work/ZoF-d4169da/include/sys/lua/lua.h:13:
> In file included from /tmp/usr/ports/sysutils/openzfs-kmod/work/ZoF-d4169da/include/sys/zfs_context.h:45:
> In file included from /tmp/usr/ports/sysutils/openzfs-kmod/work/ZoF-d4169da/include/os/freebsd/spl/sys/kobj.h:41:
> /tmp/usr/ports/sysutils/openzfs-kmod/work/ZoF-d4169da/include/os/freebsd/spl/sys/vnode.h:281:17: error: too many arguments to function call, expected single argument 'vp', have 2 arguments
>         VOP_UNLOCK(vp, 0);
>         ~~~~~~~~~~     ^
> ./vnode_if.h:892:1: note: 'VOP_UNLOCK' declared here
> static __inline int VOP_UNLOCK(
> ^
> 2 errors generated.
>
> A+
> Dave
> _______________________________________________
> freebsd-fs@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-fs
> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org"

--
Ryan Moeller
iXsystems, Inc.
OS Developer
Email: ryan@iXsystems.com



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