Received: by 10.43.115.73 with SMTP id fd9mr2128000icc.2.1346729326079;
        Mon, 03 Sep 2012 20:28:46 -0700 (PDT)
X-BeenThere: python-on-a-chip@googlegroups.com
Received: by 10.231.74.223 with SMTP id v31ls10563088ibj.0.gmail; Mon, 03 Sep
 2012 20:28:45 -0700 (PDT)
Received: by 10.42.90.4 with SMTP id i4mr8650427icm.19.1346729325580;
        Mon, 03 Sep 2012 20:28:45 -0700 (PDT)
Received: by 10.42.90.4 with SMTP id i4mr8650426icm.19.1346729325571;
        Mon, 03 Sep 2012 20:28:45 -0700 (PDT)
Return-Path: <dwhall...@gmail.com>
Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182])
        by gmr-mx.google.com with ESMTPS id wo9si1427852igc.1.2012.09.03.20.28.45
        (version=TLSv1/SSLv3 cipher=OTHER);
        Mon, 03 Sep 2012 20:28:45 -0700 (PDT)
Received-SPF: pass (google.com: domain of dwhall...@gmail.com designates 209.85.223.182 as permitted sender) client-ip=209.85.223.182;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of dwhall...@gmail.com designates 209.85.223.182 as permitted sender) smtp.mail=dwhall...@gmail.com; dkim=pass header...@gmail.com
Received: by iebc12 with SMTP id c12so7191308ieb.27
        for <python-on-a-chip@googlegroups.com>; Mon, 03 Sep 2012 20:28:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=content-type:mime-version:subject:from:in-reply-to:date
         :content-transfer-encoding:message-id:references:to:x-mailer;
        bh=BNS0ggiTG0DJAfsoZp2kkR9gZIDitR865JpV0xilSc0=;
        b=IpARQEtumgYirWM2tEqZUUqH8g0aXnG0/XElHWmMsVn4E+39r0d3d4wEm02PrC63j5
         2GG0pdjzzSe4ESVAyPWxL/r+jDukfBAh7tzfUbAL2Jw32/nDyOi6Z3QXsmVWDG3TRZDD
         Oxou3D7Ybyl3Q6X9UzoNa9IVKqFM1vHTrf5eoAs95tXnazMXHtTnOV43ZwMMdZrdgqn7
         AD4RlDIbkU3UPZsZH9PnTaCwrab+uf6bnfLxPyAWzMAiWNVnBQl+0y4OsDsClBQtp12h
         JUEfwYkSCB6pagv6Kmv5KXmWkgsYr3qwVzs/qTa8FR0z1DmTqZQcY7+j3+KTFt8v1dbI
         EubA==
Received: by 10.42.123.130 with SMTP id s2mr16797385icr.50.1346729325459;
        Mon, 03 Sep 2012 20:28:45 -0700 (PDT)
Return-Path: <dwhall...@gmail.com>
Received: from [192.168.15.127] (c-24-9-22-93.hsd1.co.comcast.net. [24.9.22.93])
        by mx.google.com with ESMTPS id ch4sm11087723igb.2.2012.09.03.20.28.43
        (version=TLSv1/SSLv3 cipher=OTHER);
        Mon, 03 Sep 2012 20:28:44 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: [python-on-a-chip] Problem with compiling v9 for econotag
From: Dean Hall <dwhall...@gmail.com>
In-Reply-To: <43178d3a-702c-4bba-b3b5-ab6ecb7c8990@googlegroups.com>
Date: Mon, 3 Sep 2012 21:28:42 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <2CDCF83D-CA67-40D6-AE87-C4D256552...@gmail.com>
References: <43178d3a-702c-4bba-b3b5-ab6ecb7c8990@googlegroups.com>
To: python-on-a-chip@googlegroups.com
X-Mailer: Apple Mail (2.1084)

Sorry, I'm no help.  I have trouble with the arm-* GCC toolchain.
I'm on a macbook, so I use the yagarto distro for arm-none-eabi-

!!Dean

On Sep 1, 2012, at 2:25 AM, Radomir wrote:

> Does anyone know how to compile code for econotag platform (mc13224) =
with jsnyder's arm-eabi-toolchain?
> I have got: "error: AAPCS does not support =
-mcallee-super-interworking"
>=20
> ---
> Radomir
>=20
> --=20
> You are subscribed to the "python-on-a-chip" (or p14p for short) =
Google Group.
> Site: http://groups.google.com/group/python-on-a-chip