[Buildroot] Buildroot 2010.05-rc3 released

[Microbit_Ubuntu <microbit@virginbroadband.com.au>]

A propos,

On Thu, 2010-05-27 at 23:15 +0200, Yann E. MORIN wrote:
> Kris, All,
> 
> On Thursday 27 May 2010 20:58:43 Microbit_Ubuntu wrote:
> [--SNIP--]
> > PS : ct-ng only offers "linuxthreads".
> 
> That's only true if you build a uClibc-based toolchain. If you build a
> glibc- or a eglibc-based toolchain, then crosstool-NG allows you to
> use NPTL.
> 
> So I'll take that you build a uClibc-based toolchain...
> 
> > So are we supposed to use 
> > "stable/old" in BR or "new" (latter, I guess) ????
> 
> That has to match the way you configured uClibc in your toolchain.
> Check the uClibc .config file for that.
> 
> > 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 ?
> 
> libthread_db.so.1 is dlopen(3)ed by gdbserver, so you have to get it on
> your target, in the standard libraries search path.
> 
> Also, there is a known dangling issue wrt cross-gdb + gdbserver.
> See this thread:
>   http://lists.busybox.net/pipermail/buildroot/2010-May/034435.html
> 
> In short, you have to get the cross-gdb *and* the gdbserver from the
> same version of gdb, to be sure they know how to speak to each other.
> So: either get both from crosstool-NG, or get both from buildroot.
> 
> Regards,
> Yann E. MORIN.
> 




> libthread_db.so.1 is dlopen(3)ed by gdbserver, so you have to get it on
> your target, in the standard libraries search path.

When gdbserver was bleating about libthread_db.so.1, it was in the staging directory,
but it wasn't placed on the target rootfs.
When I manually added it on the target (libthread_db.so.1 I mean), gdbserver worked good as gold then...

-- Kris