From: Microbit_Ubuntu <microbit@virginbroadband.com.au>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot 2010.05-rc3 released
Date: Fri, 28 May 2010 04:58:43 +1000 [thread overview]
Message-ID: <1274986723.7293.8.camel@ubuntu> (raw)
In-Reply-To: <877hmpv7km.fsf@macbook.be.48ers.dk>
Hi Peter,
On Thu, 2010-05-27 at 14:43 +0200, Peter Korsgaard wrote:
> Hi,
>
> Buildroot 2010.05-rc3 is released - Go download it at:
>
> http://buildroot.net/downloads/buildroot-2010.05-rc3.tar.gz
>
> or
>
> http://buildroot.net/downloads/buildroot-2010.05-rc3.tar.bz2
>
> Or get it from Git:
>
> git://git.buildroot.net/buildroot
>
> Please give it a spin and report any problems to the mailing list or bug
> tracker. Many thanks to the people contributing to this release:
>
> git shortlog -s -n 2010.05_rc2..
> 49 Peter Korsgaard
> 32 Thomas Petazzoni
> 1 Baruch Siach
> 1 Bj?rn Forsman
> 1 H Hartley Sweeten
> 1 Julien Boibessot
> 1 Nick Leverton
> 1 Yann E. MORIN
> 1 cmchao
>
> Unless any big issues are found, expect the final 2010.05 release by the
> end of the week - So please give it a good test.
>
> --
> Bye, Peter Korsgaard
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
While I started a clean install w/ ext toolchain (crosstool-ng -1.6.1),
I noticed that menuconfig still has a snag in it when starting from
scratch with config :
When HAL is not used and ext toolchain selected, udev & hotplug are
*not* displayed nor selected.
busybox-show-others has to be enabled and they both have to be
explicitly enabled from there.
BR versions < 2009.11 turned 'em on when mdev was selected.
Perhaps it's deemed that HAL should be selected, dunno.
In any case, hotplug & udev should not be suppressed by SHOW_OTHERS,
since even busybox-1.16.1 does NOT offer them...
More feedback when I completely rebuild.
PS : ct-ng only offers "linuxthreads". So are we supposed to use
"stable/old" in BR or "new" (latter, I guess) ????
I seem to have had problems with that - invoking gdbserver prompts :
"can't load libthread_db.so.1".
This worked fine with internal toolchain... Anyone ?
HTH
Best regards,
Kris
next prev parent reply other threads:[~2010-05-27 18:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 12:43 [Buildroot] Buildroot 2010.05-rc3 released Peter Korsgaard
2010-05-27 18:58 ` Microbit_Ubuntu [this message]
2010-05-27 21:15 ` Yann E. MORIN
2010-05-27 21:51 ` Microbit_Ubuntu
2010-05-27 21:55 ` Microbit_Ubuntu
2010-05-28 20:20 ` Yann E. MORIN
2010-06-01 10:21 ` Microbit_Ubuntu
2010-06-01 10:57 ` Peter Korsgaard
2010-06-01 18:25 ` Microbit_Ubuntu
2010-06-01 20:21 ` Microbit_Ubuntu
2010-06-01 20:27 ` Yann E. MORIN
2010-05-28 0:49 ` Microbit_Ubuntu
2010-05-27 21:11 ` [Buildroot] Buildroot 2010.05-rc3 released uClibc 0.9.30.1 patches missing ? Microbit_Ubuntu
2010-05-27 21:19 ` Yann E. MORIN
2010-05-27 21:32 ` Microbit_Ubuntu
2010-05-28 12:44 ` Peter Korsgaard
2010-06-01 10:38 ` Microbit_Ubuntu
2010-06-01 11:00 ` Peter Korsgaard
2010-05-28 0:37 ` [Buildroot] Buildroot 2010.05-rc3 released :: 2 build errors - lockfile-progs & gdb Microbit_Ubuntu
2010-05-30 7:35 ` Peter Korsgaard
2010-06-01 10:23 ` Microbit_Ubuntu
2010-06-01 10:56 ` Peter Korsgaard
2010-06-01 18:30 ` Microbit_Ubuntu
2010-06-15 7:10 ` Thomas Petazzoni
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=1274986723.7293.8.camel@ubuntu \
--to=microbit@virginbroadband.com.au \
--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.