Re: 14-CURRENT/aarch64 build problem
On 6/8/21 3:42 PM, Juraj Lutter wrote: On 8 Jun 2021, at 21:38, bob prohaska wrote: FWIW, same problem seen here. In an added twist, git pull (hoping for a fix) fails also: root@www:/usr/src # git pull error: cannot lock ref 'refs/remotes/freebsd/vendor/openzfs/legacy': 'refs/remotes/freebsd/vendor/openzfs' exists; cannot create 'refs/remotes/freebsd/vendor/openzfs/legacy' From https://git.freebsd.org/src ! [new branch] vendor/openzfs/legacy -> freebsd/vendor/openzfs/legacy (unable to update local ref) error: cannot lock ref 'refs/remotes/freebsd/vendor/openzfs/master': 'refs/remotes/freebsd/vendor/openzfs' exists; cannot create 'refs/remotes/freebsd/vendor/openzfs/master' ! [new branch] vendor/openzfs/master -> freebsd/vendor/openzfs/master (unable to update local ref) error: cannot lock ref 'refs/remotes/freebsd/vendor/openzfs/zfs-2.1-release': 'refs/remotes/freebsd/vendor/openzfs' exists; cannot create 'refs/remotes/freebsd/vendor/openzfs/zfs-2.1-release' ! [new branch] vendor/openzfs/zfs-2.1-release -> freebsd/vendor/openzfs/zfs-2.1-release (unable to update local ref) Is this a problem at my end, or the server's end? This already has been documented, as the old openzfs branch has been renamed/moved. $ git remote prune freebsd $ git pull See: https://lists.freebsd.org/archives/freebsd-git/2021-June/15.html Having pulled a completely new tree (rm -rf /usr/src/*; git clone), I get the following failure .. did I miss something? ===> cddl/lib/libicp_rescue (obj,all,install) Building /usr/obj/usr/src/amd64.amd64/cddl/lib/libicp_rescue/libicp_rescue.so.3 building shared library libicp_rescue.so.3 Building /usr/obj/usr/src/amd64.amd64/cddl/lib/libicp_rescue/_libinstall ===> cddl/lib/libspl (obj,all,install) make[4]: make[4]: don't know how to make atomic.S. Stop `assert.c' is up to date. `list.c' is up to date. `mkdirp.c' is up to date. `page.c' is up to date. `timestamp.c' is up to date. `zone.c' is up to date. `include/sys/list.h' is up to date. `include/sys/list_impl.h' is up to date. `getexecname.c' is up to date. `gethostid.c' is up to date. `getmntany.c' is up to date. `mnttab.c' is up to date. `atomic.S' was not built (being made, type OP_DEPS_FOUND|OP_MARK, flags REMAKE|DONE_WAIT|DONE_ALLSRC|DONECYCLE)! `afterdepend' was not built (deferred, type OP_DEPENDS|OP_NOTMAIN|OP_PHONY|OP_DEPS_FOUND|OP_MARK, flags REMAKE|DONE_WAIT|DONECYCLE)! `afterdepend' has .ORDER dependency against .depend (deferred, type OP_DEPENDS|OP_NOPATH|OP_DEPS_FOUND|OP_MARK, flags REMAKE|DONE_WAIT|CYCLE|DONECYCLE) `assert.o' was not built (unmade, type OP_DEPENDS|OP_NOPATH|OP_HAS_COMMANDS|OP_DEPS_FOUND|OP_MARK, flags REMAKE|DONE_WAIT|DONECYCLE)! `list.o' was not built (unmade, type OP_DEPENDS|OP_NOPATH|OP_HAS_COMMANDS|OP_DEPS_FOUND|OP_MARK, flags REMAKE|DONE_WAIT|DONECYCLE)! ` [ .. etc. .. ] imb
Re: 14-CURRENT/aarch64 build problem
> On 8 Jun 2021, at 21:38, bob prohaska wrote: > > FWIW, same problem seen here. In an added twist, git pull (hoping for > a fix) fails also: > > root@www:/usr/src # git pull > error: cannot lock ref 'refs/remotes/freebsd/vendor/openzfs/legacy': > 'refs/remotes/freebsd/vendor/openzfs' exists; cannot create > 'refs/remotes/freebsd/vendor/openzfs/legacy' > From https://git.freebsd.org/src > ! [new branch] vendor/openzfs/legacy -> > freebsd/vendor/openzfs/legacy (unable to update local ref) > error: cannot lock ref 'refs/remotes/freebsd/vendor/openzfs/master': > 'refs/remotes/freebsd/vendor/openzfs' exists; cannot create > 'refs/remotes/freebsd/vendor/openzfs/master' > ! [new branch] vendor/openzfs/master -> > freebsd/vendor/openzfs/master (unable to update local ref) > error: cannot lock ref 'refs/remotes/freebsd/vendor/openzfs/zfs-2.1-release': > 'refs/remotes/freebsd/vendor/openzfs' exists; cannot create > 'refs/remotes/freebsd/vendor/openzfs/zfs-2.1-release' > ! [new branch] vendor/openzfs/zfs-2.1-release -> > freebsd/vendor/openzfs/zfs-2.1-release (unable to update local ref) > > Is this a problem at my end, or the server's end? This already has been documented, as the old openzfs branch has been renamed/moved. $ git remote prune freebsd $ git pull See: https://lists.freebsd.org/archives/freebsd-git/2021-June/15.html otis — Juraj Lutter o...@freebsd.org
Re: 14-CURRENT/aarch64 build problem
On Tue, Jun 08, 2021 at 09:15:37PM +0200, Juraj Lutter wrote: > Hi, > > I???m having problem to build recent 14-CURRENT/aarch64 as of > 6d2648bcaba9b14e2f5c76680f3e7608e1f125f4: > > --- cddl/lib/libuutil__L --- > make[4]: make[4]: don't know how to make uu_dprintf.c. Stop > make[4]: make[4]: don't know how to make uu_open.c. Stop > `uu_alloc.c' is up to date. > `uu_avl.c' is up to date. > `uu_dprintf.c' was not built (being made, type OP_DEPS_FOUND|OP_MARK, flags > REMAKE|DONE_WAIT|DONE_ALLSRC|DONECYCLE)! > ??? > > The build is performed with pristine /usr/obj > FWIW, same problem seen here. In an added twist, git pull (hoping for a fix) fails also: root@www:/usr/src # git pull error: cannot lock ref 'refs/remotes/freebsd/vendor/openzfs/legacy': 'refs/remotes/freebsd/vendor/openzfs' exists; cannot create 'refs/remotes/freebsd/vendor/openzfs/legacy' >From https://git.freebsd.org/src ! [new branch] vendor/openzfs/legacy -> freebsd/vendor/openzfs/legacy (unable to update local ref) error: cannot lock ref 'refs/remotes/freebsd/vendor/openzfs/master': 'refs/remotes/freebsd/vendor/openzfs' exists; cannot create 'refs/remotes/freebsd/vendor/openzfs/master' ! [new branch] vendor/openzfs/master -> freebsd/vendor/openzfs/master (unable to update local ref) error: cannot lock ref 'refs/remotes/freebsd/vendor/openzfs/zfs-2.1-release': 'refs/remotes/freebsd/vendor/openzfs' exists; cannot create 'refs/remotes/freebsd/vendor/openzfs/zfs-2.1-release' ! [new branch] vendor/openzfs/zfs-2.1-release -> freebsd/vendor/openzfs/zfs-2.1-release (unable to update local ref) Is this a problem at my end, or the server's end? Thanks for reading, bob prohaska
14-CURRENT/aarch64 build problem
Hi, I’m having problem to build recent 14-CURRENT/aarch64 as of 6d2648bcaba9b14e2f5c76680f3e7608e1f125f4: --- cddl/lib/libuutil__L --- make[4]: make[4]: don't know how to make uu_dprintf.c. Stop make[4]: make[4]: don't know how to make uu_open.c. Stop `uu_alloc.c' is up to date. `uu_avl.c' is up to date. `uu_dprintf.c' was not built (being made, type OP_DEPS_FOUND|OP_MARK, flags REMAKE|DONE_WAIT|DONE_ALLSRC|DONECYCLE)! … The build is performed with pristine /usr/obj Any hints, please? Thanks otis — Juraj Lutter o...@freebsd.org
