From: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] [BR-AVR32] Re: Shell-Weirdness
Date: Tue, 25 Mar 2008 08:12:19 +0100 [thread overview]
Message-ID: <1206429139.19642.12.camel@localhost> (raw)
In-Reply-To: <46a136670803201032p55b8aa2dx91dd48fae97c79a3@mail.gmail.com>
On Thu, 2008-03-20 at 13:32 -0400, John Voltz wrote:
> Wow. That stinks. I'll forward this message to the Atmel guys and see
> if they have any idea what to do to maybe fix this.
>
The AVR32 patches for GCC (and Binutils) are vendor specific so I would
not recommend applying them to other architectures.
That is also one of the reasons it is better for the time being to
separate out the AVR32 specific stuff from Buildroot in a separate
branch.
When time comes, and stuff is properly merged, there should be very
little difference between upstream and the AVR32 branch.
--
With kind regards,
Hans-Christian Egtvedt, Applications Engineer
prev parent reply other threads:[~2008-03-25 7:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-20 13:06 [Buildroot] Shell-Weirdness Christof Klaiber
2008-03-20 17:05 ` John Voltz
2008-03-20 17:10 ` Nigel Kukard
2008-03-20 17:12 ` Nigel Kukard
2008-03-20 17:32 ` John Voltz
2008-03-25 7:12 ` Hans-Christian Egtvedt [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=1206429139.19642.12.camel@localhost \
--to=hans-christian.egtvedt@atmel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox