Date: Wed, 27 Jun 2018 10:08:11 -0700 From: Bryan Drewery <bdrewery@FreeBSD.org> To: freebsd-arch@freebsd.org Subject: Re: Building and Iterating Message-ID: <aad201f0-f270-2da2-e56a-00457c269628@FreeBSD.org> In-Reply-To: <686cb08d-5648-52f4-a95e-2faf3ea20bef@FreeBSD.org> References: <cd5d5e25-34e8-5b1b-c764-affbeabf2ea8@freebsd.org> <686cb08d-5648-52f4-a95e-2faf3ea20bef@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --CY5ujk00OEU3IABn47xLFZAJhMYfv4jMb Content-Type: multipart/mixed; boundary="19a1ModR1MTu60mUXgFqei6jDjqMHl39b"; protected-headers="v1" From: Bryan Drewery <bdrewery@FreeBSD.org> To: freebsd-arch@freebsd.org Message-ID: <aad201f0-f270-2da2-e56a-00457c269628@FreeBSD.org> Subject: Re: Building and Iterating References: <cd5d5e25-34e8-5b1b-c764-affbeabf2ea8@freebsd.org> <686cb08d-5648-52f4-a95e-2faf3ea20bef@FreeBSD.org> In-Reply-To: <686cb08d-5648-52f4-a95e-2faf3ea20bef@FreeBSD.org> --19a1ModR1MTu60mUXgFqei6jDjqMHl39b Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 6/20/2018 2:00 PM, Bryan Drewery wrote: > On 6/1/2018 10:20 AM, Sean Bruno wrote: >> Before I dive into the mk files of a buildworld, I'd like to describe >> "what I want" so as to start a discussion of my goal. >> >> 1. If I select no toolchain (WITHOUT_TOOLCHAIN), but clang needs to b= e >> built, only build a toolchain that targets the ARCH being requested. >> >> 2. If I select no toolchain (WITHOUT_TOOLCHAIN), but clang needs to b= e >> built, give me a knob to turn that aborts the build with a meaningful >> message that lets me know I need to update the toolchain on my buildbo= x. >> >=20 > https://reviews.freebsd.org/D11077 has this but I suspect it's wildly > stale already. >=20 > Also having a knob like this would ultimately lead to someone making > their /usr/bin/cc less useful for optimizations like WITH_SYSTEM_COMPIL= ER. >=20 >> 3. If the boostrap toolchain needs to be built in the normal case, on= ly >> target the ARCH being requested. I understand that we "want" a CC >> installed that targets all architectures and this is something I agree= with. >> >=20 > Hm yes there is no real reason to have multi-arch support in the > WORLDTMP compiler. Though I do have a pending patch to build clang > *once* for universe that relies on this full-arch-support behavior but > I'm sure it's trivial to continue using it for that piece. >=20 >=20 For the archives, a lot of this is effectively done now. See https://lists.freebsd.org/pipermail/freebsd-current/2018-June/069994.html= --=20 Regards, Bryan Drewery --19a1ModR1MTu60mUXgFqei6jDjqMHl39b-- --CY5ujk00OEU3IABn47xLFZAJhMYfv4jMb Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJbM8R8AAoJEDXXcbtuRpfPZLkH/0ogywC+bMM0sIjtT3auzv7e 8ugFAXo04UCu/bcE81714BsTbTTHmE5wYAPjYWIHge8v6gwC2HIW6qkJEJ7lepvg HJtleatabIitvbgI1Palg7Z/XCZYQUea6YgkmuaxZF6PSyH7qRtJS++oTgWgOopR HuywnDHO/yWSDMmy/6PWSGod3Xb4LFZq/39w2gKJCxYMyZv1vMHpX17h6yYI1ziV WW4xBzfOUY/yhsNgr2vvzwEPIzok/V4UYu80zh0sOX5FIEo3xx1vRh0cuWjgKt0N 6b9tMbBCUdNj9Em2A8YoEFNki88KTmI5edC84PCKAmT05reWPjO/cy0d/OX9HqU= =TAlw -----END PGP SIGNATURE----- --CY5ujk00OEU3IABn47xLFZAJhMYfv4jMb--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aad201f0-f270-2da2-e56a-00457c269628>