From owner-freebsd-current@FreeBSD.ORG Tue Aug 17 15:09:59 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 608261065670 for ; Tue, 17 Aug 2010 15:09:59 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from tensor.andric.com (cl-327.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:146::2]) by mx1.freebsd.org (Postfix) with ESMTP id 215AB8FC19 for ; Tue, 17 Aug 2010 15:09:59 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:2911:19d3:9b0d:9343] (unknown [IPv6:2001:7b8:3a7:0:2911:19d3:9b0d:9343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 381575C59; Tue, 17 Aug 2010 17:09:58 +0200 (CEST) Message-ID: <4C6AA64F.3050100@andric.com> Date: Tue, 17 Aug 2010 17:10:07 +0200 From: Dimitry Andric User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.2.9pre) Gecko/20100814 Lanikai/3.1.3pre MIME-Version: 1.0 To: Daniel Nebdal References: <4C6A7357.8000606@andric.com> <19F5467B-6432-4531-BF04-62D8EB4F3093@gid.co.uk> <4C6A92E0.4050104@andric.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: 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:09:59 -0000 On 2010-08-17 16:28, Daniel Nebdal wrote: > 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. Well, except when you want to bootstrap something. :) I guess this whole issue is just not as applicable to Linux, where gcc's main development takes place. > As a third possibility, hacking a real -drop-all-builtin-paths flag > into the local copies of both compilers could work The idea of method 1) is that you do not modify the compiler at all, making it potentially easier to hook in any new compilers, provided they are option-compatible with gcc.