Date: Wed, 16 Apr 2014 11:00:06 -0600 From: Warner Losh <imp@bsdimp.com> To: Jordan Hubbard <jkh@ixsystems.com> Cc: Glen Barber <gjb@FreeBSD.org>, freebsd-arm@FreeBSD.org, Ian Lepore <ian@FreeBSD.org> Subject: Re: What happened to 11-Current ARM Message-ID: <0AFC65DC-59EF-43C2-B96D-720741D31F15@bsdimp.com> In-Reply-To: <2095B803-D86F-4B1C-AE0D-575D8C878BC0@ixsystems.com> References: <534D99CB.40607@gmail.com> <20140415204516.GF33565@glenbarber.us> <1397595942.1124.125.camel@revolution.hippie.lan> <20140415211341.GG33565@glenbarber.us> <DE749EF3-4916-4A66-9FE7-24DC7F5784E5@bsdimp.com> <20140415221934.GH33565@glenbarber.us> <20140415232211.GI33565@glenbarber.us> <20140416015925.GM33565@glenbarber.us> <D911B5E9-BE2C-4C07-94AB-727E2EAE6711@FreeBSD.org> <1397654459.1124.136.camel@revolution.hippie.lan> <40D86548-EA3E-49D5-B95B-97BAC7AFB716@bsdimp.com> <2095B803-D86F-4B1C-AE0D-575D8C878BC0@ixsystems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 16, 2014, at 10:42 AM, Jordan Hubbard <jkh@ixsystems.com> wrote:
>=20
> On Apr 16, 2014, at 9:24 PM, Warner Losh <imp@bsdimp.com> wrote:
>=20
>> DEFAULT_COMPILER {clang,gcc} when set, causes a =
symlink from
>> =
cc to this value. In an ideal world
>> =
this could also be something like
>> =
/usr/local/bin/gcc48 too.
>=20
> I=92d personally find it more than a little odd to have a setting in =
/etc/make.conf in conjunction with a build create side-effects in my =
filesystem such that this behavior results:
>=20
> # cc -v
> Using built-in specs.
> Target: amd64-undermydesk-freebsd
> =85
> # cd /usr/src; make buildworld
> # cc -v
> FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610
> ..
>=20
> In other words, a build that was formerly not mutagenic to the build =
system now becomes mutagenic, unless you had some other value of =93cc=94 =
in mind than /usr/bin/cc?
I=92m talking installworld here, not buildworld, so I don=92t think this =
point is at all relevant. the behavior you describe wouldn=92t happen. =
What you suggest would never happen, and the build wouldn=92t suddenly =
become mutagenic.
> Why not simply follow existing precedent and introduce a cc-select =
command that sets up all of the appropriate symlinks? Then at least =
rather than setting a DEFAULT_COMPILER in /etc/make.conf you just run =
the command explicitly to change the default compiler and there are no =
surprises, since you did it explicitly.
Since your premise is wrong, the solution is wrong as well. All the =
above would do is replace the really quite horrible CLANG_IS_CC with =
something slightly more flexible and allow us to delete that from the =
tree forever. The base behavior wouldn=92t change as far as what happens =
to the the host system.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0AFC65DC-59EF-43C2-B96D-720741D31F15>