From owner-freebsd-current@FreeBSD.ORG Tue Aug 17 15:26:19 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 60B3410656A8 for ; Tue, 17 Aug 2010 15:26:19 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 406358FC1A for ; Tue, 17 Aug 2010 15:26:18 +0000 (UTC) Received: by pzk7 with SMTP id 7so2952788pzk.13 for ; Tue, 17 Aug 2010 08:26:18 -0700 (PDT) Received: by 10.114.66.10 with SMTP id o10mr7981053waa.113.1282057466577; Tue, 17 Aug 2010 08:04:26 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.150.135 with HTTP; Tue, 17 Aug 2010 08:04:06 -0700 (PDT) In-Reply-To: References: <4C6A7357.8000606@andric.com> <19F5467B-6432-4531-BF04-62D8EB4F3093@gid.co.uk> <4C6A92E0.4050104@andric.com> From: Eitan Adler Date: Tue, 17 Aug 2010 11:04:06 -0400 Message-ID: To: Daniel Nebdal Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: Dimitry Andric , current@freebsd.org Subject: Re: Building world with clang X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Aug 2010 15:26:19 -0000 On Tue, Aug 17, 2010 at 10:28 AM, Daniel Nebdal wrote: > On Tue, Aug 17, 2010 at 3:47 PM, Dimitry Andric wrot= e: >> 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. =C2=A0So 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. >> > > Mmh, I just read through the in-detail description you gave in another > mail. It's a bit surprising that there isn't a simple and reliable way > to disable/replace all hardcoded paths, but I guess it doesn't come up > that often. what about -nostdinc ? Do not search the standard system directories for header files. Or will this also disable the command line equivalents ? --=20 Eitan Adler