public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: hskinnemoen@atmel.com
Cc: linux-kernel@vger.kernel.org
Subject: Working upstream toolchain for avr32?
Date: Thu, 13 Dec 2007 20:56:17 +0100	[thread overview]
Message-ID: <20071213195617.GF21616@stusta.de> (raw)

AFAIK the latest available AVR32 toolchains are some patched gcc 4.0 and 
some patched binutils 2.17, and avr32 is currently the only architecture 
in the kernel where upstream of both of them is not capable of building 
a kernel for the architecture.

ALthough not technically a requirement, it would be nice if all Linux 
kernel archs could be compiled with plain upstream toolchains.

Even more since at some point in the future [1] current toolchains might 
no longer be able to compile the then current kernels.

Thanks in advance
Adrian

[1] although it might be a few years from now

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


             reply	other threads:[~2007-12-13 19:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-13 19:56 Adrian Bunk [this message]
2007-12-14  9:41 ` Working upstream toolchain for avr32? Haavard Skinnemoen
2007-12-28  8:52   ` Adrian Bunk
2007-12-14 20:03 ` Robert Schwebel
2007-12-14 20:21   ` Mike Frysinger
2007-12-14 20:28     ` Robert Schwebel
2007-12-14 20:35       ` Mike Frysinger
2007-12-14 20:55         ` Robert Schwebel
2007-12-14 21:23           ` Mike Frysinger
2007-12-14 21:59             ` Robert Schwebel

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=20071213195617.GF21616@stusta.de \
    --to=bunk@kernel.org \
    --cc=hskinnemoen@atmel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox