From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] New to embedded Linux... questions ref. buildroot
Date: Thu, 23 Oct 2008 16:48:00 +0200 [thread overview]
Message-ID: <8763njgyfz.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <6.2.5.6.2.20081023103240.02fb21b0@rkt-tech.com> (Eric's message of "Thu\, 23 Oct 2008 10\:43\:13 -0400")
>>>>> "Eric" == Eric <spamsink@scoot.netis.com> writes:
Eric> At 09:38 AM 10/23/2008, Bernhard Reutner-Fischer wrote:
>>>>>>
>> Note that the above is not buildroot (as should be mentioned somewhere
>> where you downloaded it).
Eric> <<<<<
Eric> Uhhh ... ok ...
Eric> If "buildroot-avr32-v2.2.0.tar.bz2" is not buildroot
Eric> (customized for AVR32), then what is it? I saw nothing
Eric> anywhere I visited when I downloaded it, that said it wasn't
Eric> the "real" buildroot.
It is, the point is that we don't know what those customizations are.
>> http://buildroot/uClibc.org/
Eric> That's supposed to be buildroot DOT uClibc.org, right? I tried
Eric> that and just got the page that says that there is a mailing
Eric> list and a buildroot web page. Clicking on the Downloads link
Eric> on that page and drilling down to the Daily Snapshots gives a
Eric> bunch of files with names like
Eric> buildroot-2008nnnn.tar.bz2... how are those different (except
Eric> in version and perhaps a few platform-specific content
Eric> differences) from buildroot-avr32-v2.2.0.tar.bz2?
We don't know. Ask Atmel what they have changed and why it doesn't
work for you.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2008-10-23 14:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-23 11:47 [Buildroot] New to embedded Linux... questions ref. buildroot Eric
2008-10-23 13:38 ` Bernhard Reutner-Fischer
2008-10-23 14:36 ` Peter Korsgaard
2008-10-23 14:43 ` Eric
2008-10-23 14:48 ` Peter Korsgaard [this message]
2008-10-23 15:24 ` Eric
2008-10-23 15:46 ` Peter Korsgaard
2008-10-23 15:33 ` Bernhard Reutner-Fischer
2008-10-23 15:18 ` Robert Nelson
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=8763njgyfz.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.