All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] arch support
Date: Mon, 12 Jan 2009 10:08:57 +0100	[thread overview]
Message-ID: <87d4esj3h2.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20090112100054.25c79c4f@hcegtvedt> (Hans-Christian Egtvedt's message of "Mon\, 12 Jan 2009 10\:00\:54 +0100")

>>>>> "Hans-Christian" == Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com> writes:

Hi,

 >> I just finished building the defconfigs for all the archs (uclibc
 >> 0.9.30 / kernel headers 2.6.28 / binutils 2.19 / gcc 4.3.2 except for
 >> avr32 which does it's own thing)
 >> 

 Hans-Christian> Nice, that is a good number of CPU cycles used ;)

yeah ;)

 >> avr32: ok (uclibc-0.9.29-avr32, binutils-2.17-avr32, gcc-4.2.2-avr32)

 Hans-Christian> Hmm, why is not 0.9.30 default for AVR32? It compiles
 Hans-Christian> fine with the upstream release, no extra patches
 Hans-Christian> needed.

I guess it's because of:

toolchain/Config.in:
config BR2_TOOLCHAIN_BUILDROOT
        bool "Buildroot toolchain"
        depends on !BR2_avr32

Which is from r21549 (Ulf)

and target/device/Config.in.toolchain:
choice
        prompt "Source location:"
        default BR2_TOOLCHAIN_ATMEL_AVR32_4_2_2 if BR2_avr32

Which is from r22624 (Ulf)

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2009-01-12  9:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-12  8:54 [Buildroot] arch support Peter Korsgaard
2009-01-12  9:00 ` Hans-Christian Egtvedt
2009-01-12  9:08   ` Peter Korsgaard [this message]
2009-01-12 10:33   ` Ulf Samuelsson
2009-01-12 10:35   ` Ulf Samuelsson
2009-01-12  9:07 ` Bernhard Reutner-Fischer
2009-01-12  9:22   ` Peter Korsgaard
2009-01-12 10:59 ` Hinko Kocevar
2009-01-12 11:05   ` Peter Korsgaard
2009-01-12 12:48     ` Hinko Kocevar
2009-01-12 20:17       ` Peter Korsgaard
2009-01-12 14:31 ` Hamish Guthrie
2009-01-12 14:38   ` Peter Korsgaard
2009-01-13  9:04     ` Hamish Guthrie
2009-01-13 11:40       ` Hinko Kocevar
2009-01-15 22:01     ` 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=87d4esj3h2.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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.