From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8711 invoked by alias); 1 Dec 2004 22:12:08 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 8651 invoked from network); 1 Dec 2004 22:11:59 -0000 Received: from unknown (HELO mail-out3.apple.com) (17.254.13.22) by sourceware.org with SMTP; 1 Dec 2004 22:11:59 -0000 Received: from mailgate2.apple.com (a17-128-100-204.apple.com [17.128.100.204]) by mail-out3.apple.com (8.12.11/8.12.11) with ESMTP id iB1MIev8001787 for ; Wed, 1 Dec 2004 14:18:40 -0800 (PST) Received: from relay2.apple.com (relay2.apple.com) by mailgate2.apple.com (Content Technologies SMTPRS 4.3.14) with ESMTP id ; Wed, 1 Dec 2004 14:11:58 -0800 Received: from [17.201.20.87] (mrs2.apple.com [17.201.20.87]) by relay2.apple.com (8.12.11/8.12.11) with ESMTP id iB1MBuD0017463; Wed, 1 Dec 2004 14:11:57 -0800 (PST) In-Reply-To: <20041201205053.GA4082@nevyn.them.org> References: <200412011820.iB1IKgXb028793@ignucius.se.axis.com> <78791A4E-DECE-4A88-8097-0AAB6CD99FE1@apple.com> <20041201205053.GA4082@nevyn.them.org> Mime-Version: 1.0 (Apple Message framework v679) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <24822DC7-6675-4A51-BF3E-49092B109504@apple.com> Cc: Hans-Peter Nilsson , gcc@gcc.gnu.org Content-Transfer-Encoding: 7bit From: Mike Stump Subject: Re: RFC: Replace -isysroot with --sysroot? Date: Wed, 01 Dec 2004 22:12:00 -0000 To: Daniel Jacobowitz X-SW-Source: 2004-12/txt/msg00098.txt.bz2 On Dec 1, 2004, at 12:50 PM, Daniel Jacobowitz wrote: > Could you give an example? Most of the time I've needed to use a > different set of headers, I've wanted a different set of libraries too. > That's why there's a single --with-sysroot option for both. Ah, yes, we find it useful in that exact combination. Te way in which we get it is a linker flag, -sysroot /usr/dev/sdk-previousos, and the compiler arranges to pass that flag when isysroot is given. The reason why we do it that way is the linker `knows' about a few places and we don't want to teach the compiler any more about the linker. I'd say, push this into binutils's ld, autoconf for it, and then we can just use it. On Dec 1, 2004, at 12:43 PM, Hans-Peter Nilsson wrote: > This is useful for cross-compiling, where you have different > projects/products and where you've put all headers and libraries > somewhere that's to be copied to the target (you supposedly > don't want to install a different compiler for each). Moving > the installed compiler is different. Oops, sorry, yes, conceptually, we want the same thing.