From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot: target/device target/device/Atmel/atngw1 etc...
Date: Sat, 17 Jan 2009 08:50:28 +0100 [thread overview]
Message-ID: <87wscu2wxn.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20090116223907.4517B77584@busybox.osuosl.org> (ulf@uclibc.org's message of "Fri\, 16 Jan 2009 22\:39\:06 +0000 \(UTC\)")
>>>>> "ulf" == ulf <ulf@uclibc.org> writes:
ulf> Author: ulf
ulf> Date: 2009-01-16 22:39:05 +0000 (Fri, 16 Jan 2009)
ulf> New Revision: 24891
ulf> Log:
ulf> Update broken AVR32 toolchain, and update configs for this, deprecate all but latest AVR32 toolchain
ulf> Added:
ulf> trunk/buildroot/toolchain/gcc/ext_source/Atmel/avr32/4.2.2-avr32-1.1.3/901-avr32-revert-broken-uclibc-stuff.patch
ulf> Modified:
ulf> trunk/buildroot/target/device/Atmel/atngw100/atngw100_defconfig
ulf> trunk/buildroot/target/device/Atmel/atstk100x/atstk100x_defconfig
ulf> trunk/buildroot/target/device/Config.in.toolchain
ulf> trunk/buildroot/toolchain/gcc/Config.in
ulf> trunk/buildroot/toolchain/gcc/gcc-uclibc-4.x.mk
ulf> +++ trunk/buildroot/toolchain/gcc/Config.in 2009-01-16 22:39:05 UTC (rev 24891)
ulf> @@ -32,9 +32,8 @@
ulf> bool "gcc 4.2.1"
ulf> config BR2_GCC_VERSION_4_2_2
ulf> - depends on BR2_avr32
ulf> depends on BR2_EXT_GCC_VERSION_4_2_2
ulf> - depends on BR2_DEPRECATED
ulf> + depends on BR2_DEPRECATED || BR2_avr32
ulf> bool "gcc 4.2.2"
This adds one more version for the !AVR32 archs, but OK.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2009-01-17 7:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 22:39 [Buildroot] svn commit: trunk/buildroot: target/device target/device/Atmel/atngw1 etc ulf at uclibc.org
2009-01-17 7:50 ` Peter Korsgaard [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=87wscu2wxn.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox