From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH RFC] Fix avr32 build using internal toolchain
Date: Sat, 19 Jan 2013 11:38:52 +0100 [thread overview]
Message-ID: <20130119113852.6d35aa94@skate> (raw)
In-Reply-To: <1358460970-2081-1-git-send-email-spdawson@gmail.com>
Hello Simon,
On Thu, 17 Jan 2013 22:16:10 +0000, spdawson at gmail.com wrote:
> uClibc 0.9.31.1 fails to build for avr32 using recent (3.7.x) kernel
> headers. The build failure looks like the following.
Thanks. I don't remember, do you have a specific interest in the AVR32
architecture support?
The thing is that apparently, the AVR32 gcc version we're using (gcc
4.2.x) doesn't build anymore with recent host gcc version (I think
Gustavo tested with gcc 4.6, and it doesn't build). Generally speaking,
the fact that we have to use old, patched, versions of gcc, binutils and
uClibc is severely problematic to support this architecture on the long
run.
Back in November, I got in touch with the people who were active on the
AVR32 architecture a few years back (Hans-Christian Egtvedt and H?vard
Skinnemoen), but they no longer work for Atmel and therefore don't know
what Atmel plans are regarding the AVR32 architecture.
Therefore, I'm wondering if we shouldn't mark this architecture as
deprecated.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-01-19 10:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 22:16 [Buildroot] [PATCH RFC] Fix avr32 build using internal toolchain spdawson at gmail.com
2013-01-19 10:38 ` Thomas Petazzoni [this message]
2013-01-20 11:01 ` Simon Dawson
2013-01-20 12:54 ` Gustavo Zacarias
2013-01-20 13:22 ` Simon Dawson
2013-01-20 14:22 ` Gustavo Zacarias
2013-01-20 21:24 ` Simon Dawson
2013-01-20 14:21 ` Thomas Petazzoni
2013-01-20 21:23 ` Simon Dawson
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=20130119113852.6d35aa94@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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.