From: Microbit_Ubuntu <microbit@virginbroadband.com.au>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot 2010.05-rc3 released
Date: Fri, 28 May 2010 10:49:14 +1000 [thread overview]
Message-ID: <1275007754.6387.30.camel@ubuntu> (raw)
In-Reply-To: <201005272315.11295.yann.morin.1998@anciens.enib.fr>
Hi Yann,
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.
>
I hope the list will forgive me sending to you & list.
Your posts have not reached me at all yet through busybox.net :-(
A follow-up as promised.
I'm rather surprised that the new build still bleats about 'can't load
libthread_db.so.1' when starting gdbserver...
That lib is in ../staging/lib as a symlink to libthread_db-0.9.30.1.so.
There's also a symlink in /staging/usr/lib called libthread_db.so which
points to libthread_db.so.1 - hmm.
As mentioned, the previous rootfs runs fine, however there is no trace
of this lib on the target.
I'm a bit stumped on this one.
I've used linuxthreads (new) in uclibc 0.9.30.1 config.
TIA
Ici avec beaucoup de soucis !!!
(rather than "sans soucis" :-)
-- Kris
next prev parent reply other threads:[~2010-05-28 0:49 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
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 [this message]
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=1275007754.6387.30.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.