From mint-bounce@lists.fishpool.fi Sun Jan 3 10:49:16 2010 Message-ID: <4B40BB5F.7060709@freesbee.fr> Date: Sun, 03 Jan 2010 16:44:31 +0100 From: =?ISO-8859-1?Q?Vincent_Rivi=E8re?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0 MIME-Version: 1.0 To: mint@lists.fishpool.fi Subject: Re: [MiNT] how to build native gcc for coldfire/68020 References: <4B40B376.5020301@freesbee.fr> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed X-Antivirus: avast! (VPS 100102-1, 02/01/2010), Outbound message X-Antivirus-Status: Clean X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: vincent.riviere@freesbee.fr Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id o03FnASi030476 Miro Kropacek wrote: > configure --host=m68k-atari-mint CFLAGS="-mcpu=5475 -O2 > -fomit-frame-pointer -s" > > This wont work for multilib targets or? (we'll get -m68020-60 -mcpu=5475 > expression for example) Do not mess build, host and target options. Let's assume you already have a cross-compiler on your build machine. You want to produce a cross-compiler that will run on ColdFire. So you have to add -mcpu=5475 in CFLAGS (because these are the CFLAGS for the host = the machine on which the cross-compiler you are building will run). Then that cross-compiler (running on ColdFire) will be able to produce code for all the multilib variant, as usual, using for example -m68020-60. The main idea to understand is that the CFLAGS used to build the cross-compiler are not the same as the ones used to build the target libraries. Unfortunately, as it is a bit complicated, some packages messes the CFLAGS, so we have to be careful. -- Vincent Rivière