From: "Peter Hüwe" <PeterHuewe@gmx.de>
To: buildroot@busybox.net
Subject: [Buildroot] AVR32 is broken (toolchain)
Date: Tue, 27 Jul 2010 22:39:45 +0200 [thread overview]
Message-ID: <201007272239.45547.PeterHuewe@gmx.de> (raw)
In-Reply-To: <20100722171035.0e656a6c@surf>
Am Donnerstag 22 Juli 2010 17:10:35 schrieb Thomas Petazzoni:
> BTW, if there are people working at Atmel on this list, it'd be great...
Maybe CC or write to avr32 at atmel.com ?
> On the Atmel website, it is possible to download a single zip file that
> contains tarballs for gcc, gdb, binutils and newlib. Having that in a
> single zip file is very unpractical for build systems like Buildroot.
Yeah. But since I guess it is all gpl licenced software, wouldn't it be
possible for the buildroot team to download the zip, repack it in single zips
and host/mirror them on the buildroot mirrors? Or atleast the toolchain parts
of the zip?
I know it's not a good option, but maybe it would ease the life of the
buildroot devs (i.e. you and peter :P)
>Moreover, having to register on the website (name, address, phone
> number and all the stuff) is even more inconvenient.
I know that form, and even if it looks like it is mandatory, it is not, just
click continue - even hotlinking would be possible.
Thanks,
Peter
next prev parent reply other threads:[~2010-07-27 20:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 22:02 [Buildroot] AVR32 is broken (toolchain) Thiago A. Corrêa
2010-07-22 1:52 ` Peter Hüwe
2010-07-22 2:29 ` Thiago A. Corrêa
2010-07-22 2:57 ` Peter Hüwe
2010-07-22 12:17 ` Thomas Petazzoni
2010-07-22 15:10 ` Thomas Petazzoni
2010-07-22 16:35 ` Thiago A. Corrêa
2010-07-23 19:12 ` Thiago A. Corrêa
2010-07-23 21:18 ` Thomas Petazzoni
2010-07-27 1:14 ` Peter Hüwe
2010-07-27 15:17 ` Thomas Petazzoni
2010-07-27 20:39 ` Peter Hüwe [this message]
2010-07-31 0:50 ` Bjørn Forsman
2010-07-31 4:58 ` Thiago A. Corrêa
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=201007272239.45547.PeterHuewe@gmx.de \
--to=peterhuewe@gmx.de \
--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