Date: Tue, 17 Aug 2010 15:47:12 +0200 From: Dimitry Andric <dimitry@andric.com> To: Daniel Nebdal <dnebdal@gmail.com> Cc: current@freebsd.org Subject: Re: Building world with clang Message-ID: <4C6A92E0.4050104@andric.com> In-Reply-To: <AANLkTi=wAhVDKX7vVd0Cds9zTSDQJ6vR%2BoyAbC-H_SK=@mail.gmail.com> References: <4C6A7357.8000606@andric.com> <19F5467B-6432-4531-BF04-62D8EB4F3093@gid.co.uk> <AANLkTi=wAhVDKX7vVd0Cds9zTSDQJ6vR%2BoyAbC-H_SK=@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2010-08-17 15:03, Daniel Nebdal wrote:
>>> However, a disadvantage is that the built-in search paths of the
>>> bootstrap compiler are not entirely disabled by using the -isysroot, -B
>>> and -L flags,
...
> For clarification, did you (Dimitry, that is) mean
> a) The paths are still there so they could resurface if some Makefile
> doesn't specify those flags , or
> b) they sometimes come into play even when using the appropriate flags?
Any sub-makefiles would not have to specify those flags explicitly,
since they were added to ${CC} and ${CXX}.
But what I meant is that even if you specify those flags, the compiler
still searches for headers and libraries in the base system. So if some
header is removed from /usr/src, for example, but is still available in
/usr/include, it can be erroneously picked up during buildworld.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C6A92E0.4050104>