Date: Mon, 23 Feb 2015 18:04:39 -0700 From: Ian Lepore <ian@freebsd.org> To: Brett Wynkoop <freebsd-arm@wynn.com> Cc: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: Re: kernel build fails Message-ID: <1424739879.56366.47.camel@freebsd.org> In-Reply-To: <20150223195849.2bd35212@ivory.wynn.com> References: <20150223173731.4902457d@ivory.wynn.com> <CAKtsCdfuqimQs7z1xGc1yPwBT9obSctQgj=uKFCS6dPrKCkZLQ@mail.gmail.com> <20150223195849.2bd35212@ivory.wynn.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 2015-02-23 at 19:58 -0500, Brett Wynkoop wrote: > On Mon, 23 Feb 2015 15:21:45 -0800 > Michael Mitchell <mmitchel@gmail.com> wrote: > > > i thought any arch except armv6 is currently problematic. (this is my > > experience with 10.x so far). > > > > /usr/src/sys/arm/compile/BEAGLEBONE/../../../cddl/compat/opensolaris/sys/debug_compat.h > > > /usr/src/sys/arm/compile/BEAGLEBONE/../../../arm/arm/genassym.c > > > cc: error: argument unused during compilation: > > > '-march=armv7a' [-Werror,-Wunused-command-line-argument] *** Error > > > code 1 > > > > > > Stop. > > > make[3]: stopped in /usr/src/sys/modules/dtrace/dtrace > > > *** Error code 1 > > > > > > Stop. > > > make[2]: stopped in /usr/src/sys/modules/dtrace > > > *** Error code 1 > > > > > > Stop. > > > make[1]: stopped in /usr/src/sys/modules > > > *** Error code 1 > > > > > > Stop. > > > make: stopped in /usr/src/sys/arm/compile/BEAGLEBONE > > > root@beaglebone:/usr/src/sys/arm/compile/BEAGLEBONE # > > > > > So the question is where did the -march-arm7a come from? It seems to > me it should not be in the kernel tree and someone introduced it in > error. > > Am I the only person who tries native kernel builds? > > -Brett > Why do you think -march=armv7 shouldn't be present on a build for an armv7 kernel? In fact it's now required to build the kernel correctly. I can build wandboard kernels on the wandboard. I haven't tried a bbb (because it's really too slow to build on). The real question is "why does -mcpu=arm1176jzf-s appear on your compile command line?" I wonder if the answer is that you've set the wrong CPUTYPE in make.conf or src.conf. -- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1424739879.56366.47.camel>