Date: Sun, 29 Apr 2012 16:22:35 -0700 From: Tim Kientzle <kientzle@freebsd.org> To: Warner Losh <imp@bsdimp.com> Cc: arm@freebsd.org Subject: Re: Cross-buildworld works but not native build? Message-ID: <A8B74A6F-1BAB-49C4-9DCF-E74D495A2611@freebsd.org> In-Reply-To: <495386AF-37AB-450D-B78C-2A6282083587@bsdimp.com> References: <9AD7075B-B85D-40DB-84B7-FD630B858A30@freebsd.org> <CAP%2BM-_Ev1TE7JEmSRbVPg3HRwMfsPVyNyR92X5UONdxmGryuaQ@mail.gmail.com> <495386AF-37AB-450D-B78C-2A6282083587@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 27, 2012, at 1:04 PM, Warner Losh wrote: >=20 >> On Fri, Apr 27, 2012 at 1:48 AM, Tim Kientzle <kientzle@freebsd.org> = wrote: >>> I've been working with the projects/armv6 tree and have encountered = a very confusing situation. >>>=20 >>> On i386, this works: >>> $ make TARGET_ARCH=3Darm TARGET_CPUTYPE=3Darmv6 buildworld >>>=20 >>> If I take the resulting world and run it on arm, then the following = fails (with the exact same source): >>> $ make buildworld >=20 > I think it would work in the current tree if you added = TARGET_CPUTYPE=3Darmv6 to the buildworld. >=20 > I'm hoping to fix issues like this in my armv6 patches. With that change, the current armv6 tree can successfully complete a native buildworld/installworld on BeagleBone. Next step: get buildkernel/installkernel to work. (I have most of the pieces I need; just some slogging to fit it together properly.) Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A8B74A6F-1BAB-49C4-9DCF-E74D495A2611>