Date: Sun, 15 Oct 2017 21:12:52 +0300 From: =?UTF-8?Q?Eddy_Petri=C8=99or?= <eddy.petrisor@gmail.com> To: Warner Losh <imp@bsdimp.com> Cc: mmel@freebsd.org, freebsd-arm@freebsd.org, bob prohaska <bob@www.zefox.net> Subject: Re: Difficulty with armv6 to v7 transition. Message-ID: <CAK0XTWcn54u%2BVGXm-2SVC56cg3WGSs5XextsmkrD7fShgd_dXg@mail.gmail.com> In-Reply-To: <CANCZdfp2khWQKLRqG0%2BQ-Z1WfwFKyq7xkrVau8scd=EPLkC0xQ@mail.gmail.com> References: <1507573171.84167.9.camel@freebsd.org> <20171011023356.GA57571@www.zefox.net> <CANCZdfrKYabu1-bWxX47=Lt=33e%2BFjBXCNBNiGPE7K-83KOAHA@mail.gmail.com> <CANCZdfqHfAe24q=6n8CxsHQv24j58bQLPG3z_7vi_xpGjdQzDg@mail.gmail.com> <20171011030021.GB57571@www.zefox.net> <20171013020604.GA70845@www.zefox.net> <20171013175943.GA74121@www.zefox.net> <F9F4D731-35CD-44E6-8419-D73CB98655E9@dsl-only.net> <20171014010713.GA75288@www.zefox.net> <254A2C41-59A9-4E4E-8982-ADDBAE2B5F91@dsl-only.net> <20171014021133.GB75288@www.zefox.net> <39f6419f-48f3-aaec-dfa4-3048c8a893d8@freebsd.org> <CAK0XTWeRbhghXotPT6jTosDGjD3TF00TsG%2Bes0AVsFuU-FyQVw@mail.gmail.com> <CANCZdfp2khWQKLRqG0%2BQ-Z1WfwFKyq7xkrVau8scd=EPLkC0xQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Pe 14 oct. 2017 7:54 PM, "Warner Losh" <imp@bsdimp.com> a scris: On Oct 14, 2017 10:43 AM, "Eddy Petri=C8=99or" <eddy.petrisor@gmail.com> wr= ote: Pe 14 oct. 2017 7:28 AM, "Michal Meloun" <melounmichal@gmail.com> a scris: On 14.10.2017 4:11, bob prohaska wrote: > On Fri, Oct 13, 2017 at 06:27:22PM -0700, Mark Millard wrote: >> On 2017-Oct-13, at 6:07 PM, bob prohaska <fbsd@www.zefox.net> wrote: >> >>> Seems it would have been better to replace >>> BUILD_ARCH!=3D uname -p >>> with >>> BUILD_ARCH!=3D echo armv7 >>> for present purposes. >> >> Are you starting under armv6 ? armv7 ? > I'm afraid it's a mix, due to some untimely foot-shooting. > > Uname - p reports armv7, but clang -v reports > FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on LLVM 4.0.0) > Target: armv6-unknown-freebsd12.0-gnueabihf > Thread model: posix > InstalledDir: /usr/bin > > I'll keep trying to unscramble the mess I've made until an armv7 RPI2 > snapshot is released, then start over if necessary. > > Thanks for reading! > > bob prohaska > Bob, can you please try this? setenv MACHINE_ARCH armv7; make buildworld TARGET=3Darm TARGET_ARCH=3Darmv7 I have been trying recently to add support for cross building FreeBSD from Linux and concluded that MACHINE is the system on which the build is done. At the start of the build, yes. But we set it while doing the actual cross build to the target. You mean that although at the beginning of the cross build MACHINE* relates to the build system, later it relates to some other different meaning? I don't think I found BUILD* meaning yet. That's because they are internal and should never be messed with. They are a detail we don't commit to keeping. If they matter, we have done something wrong. What are the ones "set in stone"? The ones documented in the meanwhile? Unfortunately I concluded the FreeBSD build system would really benefit from a clean-up in terms of variables and documenting their use. May I suggest creating a wiki page documenting the usage a clean up can be done? We do document most of them in build man page. That's what should be updated. It spells this stuff out. Where can I find this in the source tree? Warner Eddy Petri=C8=99or
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAK0XTWcn54u%2BVGXm-2SVC56cg3WGSs5XextsmkrD7fShgd_dXg>