From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28209 invoked by alias); 27 Aug 2005 03:05:40 -0000 Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org Received: (qmail 28194 invoked by uid 22791); 27 Aug 2005 03:05:35 -0000 Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Sat, 27 Aug 2005 03:05:35 +0000 Received: from drow by nevyn.them.org with local (Exim 4.52) id 1E8r0f-00067N-De; Fri, 26 Aug 2005 23:05:33 -0400 Date: Sat, 27 Aug 2005 03:05:00 -0000 From: Daniel Jacobowitz To: Kai Ruottu Cc: gcc-help@gcc.gnu.org, gcc@gcc.gnu.org Subject: Re: Cross Compiler Unix - Windows Message-ID: <20050827030532.GA23164@nevyn.them.org> Mail-Followup-To: Kai Ruottu , gcc-help@gcc.gnu.org, gcc@gcc.gnu.org References: <404974C1-D943-4008-8A58-4D3F51D2A2C0@makoglobal.com> <10ACCE39-AF0E-45AC-A7E5-F3695096C3D0@makoglobal.com> <04D9AE3F-0709-4F69-AAEF-2ED112C3C83D@apple.com> <430ECBFE.1020707@mbnet.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <430ECBFE.1020707@mbnet.fi> User-Agent: Mutt/1.5.8i X-SW-Source: 2005-08/txt/msg00267.txt.bz2 Most of this really doesn't deserve an answerr, but I'll give you a couple anyway. You spend a lot of time blaming people for their opinions, without any evidence that you've actually understood their opinions right. Most of what I've snipped is completely untrue. On Fri, Aug 26, 2005 at 10:59:58AM +0300, Kai Ruottu wrote: > The '--with-sysroot' tries to keep the 'proprietary' layouts even on > the cross-hosts, where people could always use the "standard install > layout for GCC", every GCC installed using just the same rules. So the > situation where all crosscompilers use their own proprietary layouts > has somehow been seen being better that trying to standardize the GCC > installation layout. No. The point of --with-sysroot is so that you can build a native compiler for some target, and a cross compiler to that same target, and have them use the same layout. The native layout is _not_ something that we can change at this date, whatever you may like to think about it. > Before trying to move the proprietary layouts into the peaceful? > land of cross, it could have been better to ask the crosscompiler > builders how they have solved these "copy the target headers and > libs from the native system and put them to work with the cross-GCCs > too" problems. Maybe then there had no reason for the '--with-sysroot'. > Does it even work as one would expect it to work, solving those '/lib' > and '/usr/lib' in the 'libc.so' script problems and so on? Of course it does. The absolute paths will be handled correctly by ld. This was done to minimize the pain of building cross compilers to "hosted" systems. It seems to have worked, since everyone I've spoken to who's used it finds it much more natural, and the process has less undocumented voodoo than the --with-headers/--with-libs setup. > better way to do just the same thing!" (Was the '--with-sysroot' made > for people who are not as clever as we cross-GCC people who were > considered being complete idiots? :-) As one of the people who implemented this, I take offense at your comments. If you couldn't tell. -- Daniel Jacobowitz CodeSourcery, LLC