Date: Sun, 4 Mar 2018 10:58:08 -0700 From: Warner Losh <imp@bsdimp.com> To: Dimitry Andric <dim@freebsd.org> Cc: Christian Ullrich <chris@chrullrich.net>, FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: "Cross" building for same architecture, different CPUTYPE Message-ID: <CANCZdfqzZrjseYZybt%2BcDv5MLJEK5uZqtGvJCnPrLC6TNtBrJg@mail.gmail.com> In-Reply-To: <D30A88D2-6DFB-4535-8735-C71A43DEEB6B@FreeBSD.org> References: <2126f358-c827-ecf0-109b-0488c5b155b6@chrullrich.net> <D30A88D2-6DFB-4535-8735-C71A43DEEB6B@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Mar 4, 2018 at 10:43 AM, Dimitry Andric <dim@freebsd.org> wrote: > Again, this depends on how exactly you are overriding CPUTYPE. I'd suggest *NOT* setting CPUTYPE and instead using TARGET_CPUTYPE to do these sorts of things. CPUTYPE is known to only work on native builds and is tricky to do in this scenario just so. It might work for 'near cross' builds, or it might not. TARGET_CPUTYPE overrides CPUTYPE that might be set in weird places and generally works a lot better. You don't need to set TARGET or TARGET_ARCH to do this, but it would work if you did that also. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfqzZrjseYZybt%2BcDv5MLJEK5uZqtGvJCnPrLC6TNtBrJg>