From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27001 invoked by alias); 11 Mar 2009 12:27:32 -0000 Received: (qmail 26992 invoked by uid 22791); 11 Mar 2009 12:27:30 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from mta-out.inet.fi (HELO jenni2.inet.fi) (195.156.147.13) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 11 Mar 2009 12:27:24 +0000 Received: from [192.168.0.42] (88.192.88.204) by jenni2.inet.fi (8.5.014) id 49B6541A000E0A8A; Wed, 11 Mar 2009 14:27:21 +0200 Message-ID: <49B7AEF3.50302@wippies.com> Date: Wed, 11 Mar 2009 12:27:00 -0000 From: Kai Ruottu User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: =?ISO-8859-1?Q?K=F6vesdi_Gy=F6rgy?= CC: gcc-help@gcc.gnu.org Subject: Re: mipsel-gcc configuration question References: <200903101616.33928.kgy@deverto.hu> <49B6A250.6040902@caviumnetworks.com> <200903111209.50128.kgy@deverto.hu> <200903111231.51278.kgy@deverto.hu> <49B7A6FD.5070101@wippies.com> In-Reply-To: <49B7A6FD.5070101@wippies.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org X-SW-Source: 2009-03/txt/msg00122.txt.bz2 Kai Ruottu wrote: > Maybe you should elaborate WHY you DON'T want to produce a normal native > GCC using configuration options like the : > > --prefix=/usr > > This is the assumed $prefix for a normal native GCC. The value you > give as $prefix has nothing to do with your "cross host", only with > the native (target) host on which you are going to install the produced > GCC. Basically all possible "stupid questions" should be asked... One possible misunderstanding may be that "one cannot use the '/usr' as the $prefix because then 'make install' would overwrite the native (cross) host stuff"... Of course it would but then one doesn't use it at all or would use some extra option like (seen via 'http://gcc.gnu.org/install/finalinstall.html') : "Installation into a temporary staging area or into a chroot jail can be achieved with the command make DESTDIR=path-to-rootdir install where path-to-rootdir is the absolute path of a directory relative to which all installation paths will be interpreted. Note that the directory specified by DESTDIR need not exist yet; it will be created if necessary." This some kind of "equivalent" to that '--with-sysroot=' used with crosstoolchains. With native tools its usability is questionable (used with custom native tools?). So the crosstoolchain keeps its target C libraries in some $sysroot, these are totally things for the alien $target. When one wants to add binutils and GCC for this "alien target things" directory, one uses commands like that : make DESTDIR=$sysroot install for the GCC component. What could be used with binutils should be found in the binutils docs. But installing binutils manually isn't that hard. But I expect some similar 'make install' option being for binutils too... So if one wants to "prepare" the stuff to be installed onto the target, by installing it first on the cross host system, that should succeed with suitable options...