Date: Wed, 18 Aug 2010 11:15:51 +0200 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: Dimitry Andric <dimitry@andric.com> Cc: current@freebsd.org Subject: Re: Building world with clang Message-ID: <86aaokb7so.fsf@ds4.des.no> In-Reply-To: <4C6A9AE7.3060704@andric.com> (Dimitry Andric's message of "Tue, 17 Aug 2010 16:21:27 %2B0200") References: <4C6A7357.8000606@andric.com> <20100817091515.4510ebfd@kan.dnsalias.net> <4C6A9AE7.3060704@andric.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Dimitry Andric <dimitry@andric.com> writes:
> Alexander Kabaev <kabaev@gmail.com> writes:
> > Does method 1) work fine with 'make buildenv'? I doubt that. I would
> > strongly suggest we should not lose this feature. I do not like the
> > idea of having to depend on -isystem in CFLAGS in such an environment.=
=20
> I have not tested make buildenv with this method, but since ${CC} is
> modified, not ${CFLAGS}, there is a reasonable chance that it might
> work. :)
I'm not a big fan of "reasonable chances" when it comes to the
toolchain.
> Note a similar method is already being using for the build32 stage on
> amd64, where ${CC} has a bunch of flags (including -isystem, -L and -B)
> appended.
No, what is used is a variant of method 1 *on top of* method 2 for a
very specific case. You need "a special version of clang" (method 2)
anyway to support cross-building.
DES
--=20
Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86aaokb7so.fsf>