Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 8 Jun 2021 16:10:13 -0400
From:      Michael Butler via freebsd-arm <freebsd-arm@freebsd.org>
To:        Juraj Lutter <otis@FreeBSD.org>
Cc:        freebsd-arm@freebsd.org, freebsd-current <freebsd-current@freebsd.org>
Subject:   Re: 14-CURRENT/aarch64 build problem
Message-ID:  <bcda2137-9b0a-0490-c3bd-7ebce5cd002a@protected-networks.net>
In-Reply-To: <CD1B8A13-1B9C-4CA1-888B-A2D88228E006@FreeBSD.org>
References:  <12319609-40E7-429A-B290-9C01B0A8ACDC@FreeBSD.org> <20210608193805.GA24803@www.zefox.net> <CD1B8A13-1B9C-4CA1-888B-A2D88228E006@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 6/8/21 3:42 PM, Juraj Lutter wrote:
> 
> 
>> On 8 Jun 2021, at 21:38, bob prohaska <fbsd@www.zefox.net> 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/000015.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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bcda2137-9b0a-0490-c3bd-7ebce5cd002a>