Date: Tue, 13 Feb 2018 13:22:28 -0600 From: Timur Tabi <timur@codeaurora.org> To: Erich Dollansky <freebsd.ed.lists@sumeritec.com> Cc: Timur Tabi <timur@codeaurora.org>, freebsd-arm@freebsd.org Subject: Re: Confused about ARM64 cross-compilation Message-ID: <CAOZdJXVT54VGVt9guvPFXwYhkpCBhQmFH=_JrLJqR%2BsqsoTnXQ@mail.gmail.com> In-Reply-To: <20180209172005.0b787bca.freebsd.ed.lists@sumeritec.com> References: <CAOZdJXXPFfQFGRuFrGHvkmi2wRTDq4ESBPu%2BWxXjzL=a=d3jdQ@mail.gmail.com> <20180209172005.0b787bca.freebsd.ed.lists@sumeritec.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Feb 9, 2018 at 3:20 AM, Erich Dollansky <freebsd.ed.lists@sumeritec.com> wrote: > when I did arm64 compilations, I used CURRENT as certain things did not > work in older versions. You might also try 12.0 or CURRENT. > > FreeBSD cross compiles out of the box. Of course, only for supported > targets. arm64_build.sh produces several errors when it tries to setup the rootfs for QEMU, which I'm not using. KERNEL=kernel install thiskernel=`sysctl -n kern.bootfile` ; if [ ! "`dirname "$thiskernel"`" -ef /usr/home/ubuntu/arm64-workspace/rootfs/boot/kernel ] ; then chflags -R noschg /usr/home/ubuntu/arm64-workspace/rootfs/boot/kernel ; rm -rf /usr/home/ubuntu/arm64-workspace/rootfs/boot/kernel ; rm -rf /usr/home/ubuntu/arm64-workspace/rootfs/usr/lib/debug/boot/kernel ; else if [ -d /usr/home/ubuntu/arm64-workspace/rootfs/boot/kernel.old ] ; then chflags -R noschg /usr/home/ubuntu/arm64-workspace/rootfs/boot/kernel.old ; rm -rf /usr/home/ubuntu/arm64-workspace/rootfs/boot/kernel.old ; fi ; mv /usr/home/ubuntu/arm64-workspace/rootfs/boot/kernel /usr/home/ubuntu/arm64-workspace/rootfs/boot/kernel.old ; if [ -n "/usr/lib/debug" -a -d /usr/home/ubuntu/arm64-workspace/rootfs/usr/lib/debug/boot/kernel ]; then rm -rf /usr/home/ubuntu/arm64-workspace/rootfs/usr/lib/debug/boot/kernel.old ; mv /usr/home/ubuntu/arm64-workspace/rootfs/usr/lib/debug/boot/kernel /usr/home/ubuntu/arm64-workspace/rootfs/usr/lib/debug/boot/kernel.old ; fi ; sysctl kern.bootfile=/usr/home/ubuntu/arm64-workspace/rootfs/boot/kernel.old/"`basename "$thiskernel"`" ; fi mkdir -p /usr/home/ubuntu/arm64-workspace/rootfs/boot/kernel install -U -M /usr/home/ubuntu/arm64-workspace/rootfs//METALOG -D /usr/home/ubuntu/arm64-workspace/rootfs -p -m 555 -o root -g wheel kernel /usr/home/ubuntu/arm64-workspace/rootfs/boot/kernel/ mkdir -p /usr/home/ubuntu/arm64-workspace/rootfs/usr/lib/debug/boot/kernel install -U -M /usr/home/ubuntu/arm64-workspace/rootfs//METALOG -D /usr/home/ubuntu/arm64-workspace/rootfs -p -m 555 -o root -g wheel kernel.debug /usr/home/ubuntu/arm64-workspace/rootfs/usr/lib/debug/boot/kernel/ -------------------------------------------------------------- >>> Installing kernel GENERIC completed on Tue Feb 13 12:47:40 CST 2018 -------------------------------------------------------------- METALOG:10: warning: tags: unsupported keyword METALOG:56: warning: duplicate definition of var METALOG:59: warning: tags: unsupported keyword METALOG:60: warning: tags: unsupported keyword The METALOG errors continue for another 22,000 lines. Should I just edit the script to abort before it starts doing this, or is it failing because I don't have QEMU installed? Also, why is that every time I run arm64_build.sh, it rebuilds almost everything, even when I haven't changed any files? -- Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc. Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOZdJXVT54VGVt9guvPFXwYhkpCBhQmFH=_JrLJqR%2BsqsoTnXQ>