From mint-bounce@lists.fishpool.fi Sun Jan 3 11:27:07 2010 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=1/iDh9vfqzcllLqd97yDI1ULwSVDh4JDzPBhCGZuxsU=; b=S0fWhrDn4r79gE7nId47AgfCs2qnuPLLkvi0irYerroQj2JqtWnBWuJ2K5RHo3MoOU 014mKR7Nf9CaFU7+EQwdFBUrA2V5WceZhkp+DKQ7psjXx1t90qLuKzU85RJQUxdynZ8Z 4+XD0cyz6SrtCK+QK0N0RDO/bzLrAsePmZBms= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=muGsnfcbx9/cO0sT2nWB5TlkvUV9g67XA64yHI3Tn0Ou0E01QDPauySQ5b4T/HDt2a bsR+fqpqM1XLpFLXKZgS7IGwx+gD/DZ9TGPft/F1tWnnuMOATy8yweTfEtmfWCKqoFoD wXW/aAqldtayBl+aMLjDRjqet4dy11ImG6isY= MIME-Version: 1.0 In-Reply-To: <4B40BB5F.7060709@freesbee.fr> References: <4B40B376.5020301@freesbee.fr> <4B40BB5F.7060709@freesbee.fr> Date: Sun, 3 Jan 2010 17:24:06 +0100 Message-ID: Subject: Re: [MiNT] how to build native gcc for coldfire/68020 From: Miro Kropacek To: =?ISO-8859-1?Q?Vincent_Rivi=E8re?= Cc: mint@lists.fishpool.fi Content-Type: multipart/alternative; boundary=000325554592a1de55047c450804 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: miro.kropacek@gmail.com Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: --000325554592a1de55047c450804 Content-Type: text/plain; charset=ISO-8859-1 > Do not mess build, host and target options. > We probably don't understand each other. CFLAGS changes compiler flags globally, i.e. for gcc binary, for libgcc targets, libstdc++ targets etc. So when libgcc should be build for 5475 and we set CFLAGS with m68020-60, there's a clash because commandline looks like: m68k-atari-mint-gcc -mcpu=5475 -o conftest -g -m68020-60 -O2 -fomit-frame-pointer conftest.c (confirmed by test) so I was asking for some solution where the right things get CFLAGS with m68020-60 and the multilib things get the original CFLAGS and I thought --with-arch=XYZ could help but it's not supported. -- MiKRO / Mystic Bytes http://mikro.atari.org --000325554592a1de55047c450804 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable =A0
Do not mess build, host and target options.
We= probably don't understand each other. CFLAGS changes compiler flags gl= obally, i.e. for gcc binary, for libgcc targets, libstdc++ targets etc. So = when libgcc should be build for 5475 and we set CFLAGS with m68020-60, ther= e's a clash because commandline looks like:

m68k-atari-mint-gcc=A0 -mcpu=3D5475 -o conftest -g -m68020-60 -O2 -fomi= t-frame-pointer=A0=A0=A0 conftest.c

(confirmed by test) so I was as= king for some solution where the right things get CFLAGS with m68020-60 and= the multilib things get the original CFLAGS and I thought --with-arch=3DXY= Z could help but it's not supported.

--
MiKRO / Mystic Bytes
http://mikro.atari.org
--000325554592a1de55047c450804--