Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot:target/devicetarget/device/ARMLTD targ etc...
Date: Fri, 28 Mar 2008 22:34:57 +0100	[thread overview]
Message-ID: <00b101c8911b$96d0f400$6c01a8c0@atmel.com> (raw)
In-Reply-To: 1206739421.3224.91.camel@nigel-x60

> Could you show me what I did wrong, 
> I'm busy committing the patches now for 4.2.2.
> 
> Got no problem in reverting if you can show me where I messed up?

gcc-4.2.2 has not been ported to the AVR32,
so you have obviously not built a toolchain.

Even the Atmel defconfigs for the AT91 should not be updated
to gcc-4.2.1 before they have been tested on target H/W.
Unless you have booted Linux, don't touch them.

Others may object to updating compiler versions
of their targets, without testing.

Best Regards
Ulf Samuelsson

  reply	other threads:[~2008-03-28 21:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-28 21:03 [Buildroot] svn commit: trunk/buildroot: target/device target/device/ARMLTD targ etc nkukard at uclibc.org
2008-03-28 21:08 ` Peter Korsgaard
2008-03-28 21:18   ` Bernhard Fischer
2008-03-28 21:27     ` Peter Korsgaard
2008-03-28 21:31       ` Nigel Kukard
2008-03-28 21:42       ` Bernhard Fischer
2008-03-28 21:13 ` [Buildroot] svn commit: trunk/buildroot: target/devicetarget/device/ARMLTD " Ulf Samuelsson
2008-03-28 21:23   ` Nigel Kukard
2008-03-28 21:34     ` Ulf Samuelsson [this message]
2008-03-28 22:11       ` [Buildroot] svn commit: trunk/buildroot:target/devicetarget/device/ARMLTD " Nigel Kukard
2008-03-28 22:23         ` [Buildroot] svn commit:trunk/buildroot:target/devicetarget/device/ARMLTD " Ulf Samuelsson

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='00b101c8911b$96d0f400$6c01a8c0@atmel.com' \
    --to=ulf.samuelsson@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