All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen@asianux.com>
To: Hans-Christian Egtvedt <egtvedt@samfundet.no>
Cc: "Håvard Skinnemoen" <hskinnemoen@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Linux-Arch <linux-arch@vger.kernel.org>
Subject: Re: [Suggestion] arch: avr32: compiler: compiling tools issue
Date: Tue, 25 Jun 2013 15:43:07 +0800	[thread overview]
Message-ID: <51C94A0B.7070002@asianux.com> (raw)
In-Reply-To: <20130625064800.GB23182@samfundet.no>

On 06/25/2013 02:48 PM, Hans-Christian Egtvedt wrote:
> Around Tue 25 Jun 2013 11:14:14 +0800 or thereabout, Chen Gang wrote:
>> > Hello Maintainers:
>> > 
>> > With allmodconfig, and set "avr32-linux-gnu-" as cross compiler prefix.
>> > 
>> > It will report error:
>> >   avr32-linux-gnu-gcc: error: unrecognized command line option ‘-mno-pic’
>> >   avr32-linux-gnu-gcc: error: unrecognized command line option ‘-march=ap’
>> > 
>> > The related gcc version:
>> >   [root@dhcp122 linux-next]# rpm -qf /usr/bin/avr32-linux-gnu-gcc
>> >   gcc-avr32-linux-gnu-4.7.1-0.1.20120606.fc17.x86_64
> Interesting version, 4.7.1.
> 
>> > Can we say: it is compiler's issue, and I need try to compile the cross
>> > compiler to test it again ?
> I would assume so, I didn't know Atmel finally pushed all the source code to
> support avr32-linux from upstream.
> 
> I still use a jay old 4.2 based GCC port, which was the last one I used when
> working for Atmel.

Is it possible to use the compiler tools (may from source code and
compile the compiler tools firstly), to compile the latest upstream
kernel (e.g next-20130624) for avr32 ?

Thanks.
-- 
Chen Gang

Asianux Corporation

      reply	other threads:[~2013-06-25  7:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-25  3:14 [Suggestion] arch: avr32: compiler: compiling tools issue Chen Gang
2013-06-25  6:48 ` Hans-Christian Egtvedt
2013-06-25  7:43   ` Chen Gang [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51C94A0B.7070002@asianux.com \
    --to=gang.chen@asianux.com \
    --cc=egtvedt@samfundet.no \
    --cc=hskinnemoen@gmail.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.