From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3523 invoked by alias); 16 Aug 2004 23:20:54 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 3512 invoked by alias); 16 Aug 2004 23:20:53 -0000 Date: Mon, 16 Aug 2004 23:20:00 -0000 Message-ID: <20040816232053.3510.qmail@sourceware.org> From: "wilson at specifixinc dot com" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20040816002338.17043.peterc@gelato.unsw.edu.au> References: <20040816002338.17043.peterc@gelato.unsw.edu.au> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug target/17043] Can't build a compiler that works for big and littleendian targets X-Bugzilla-Reason: CC X-SW-Source: 2004-08/txt/msg01588.txt.bz2 List-Id: ------- Additional Comments From wilson at specifixinc dot com 2004-08-16 23:20 ------- Subject: Re: New: Can't build a compiler that works for big and littleendian targets peterc at gelato dot unsw dot edu dot au wrote: > arm-linux-gcc --mbigendian -c Normally linux targets aren't bi-endian. A little-endian kernel won't run big-endian code and vice versa, so there is little point in making them bi-endian. And if the native compiler isn't bi-endian, then a cross compiler won't be either. You may have to do a litting porting work if you really need this. There is also the question of whether you have bi-endian system libraries, and if so, how they are organized. Also, I'd recommend against use of --prefix=/usr for a cross compiler, and I'd suggest using --sysroot= to specify where the target libraries and header files are. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17043