Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-devel@openembedded.org,
	David Huggins-Daines <dhuggins@cs.cmu.edu>
Subject: Re: [PATCH] Supply uclibc-thread-db package expected by	task-sdk-base
Date: Fri, 17 Apr 2009 15:35:50 -0700	[thread overview]
Message-ID: <20090417223550.GA15643@gmail.com> (raw)
In-Reply-To: <20090416171150.GI17629@smtp.west.cox.net>

On (16/04/09 10:11), Tom Rini wrote:
> On Thu, Apr 16, 2009 at 01:00:02PM -0400, David Huggins-Daines wrote:
> > Tom Rini wrote:
> > > On Tue, Apr 14, 2009 at 04:05:18PM -0400, David Huggins-Daines wrote:
> > >
> > >   
> > >> Currently, building task-sdk-base (and by extension meta-toolchain) fails
> > >> for uclibc targets.  This is because task-sdk-base depends on the thread
> > >> debugging library uclibc-thread-db, but this is not built by the uclibc
> > >> recipe unless PTHREADS_DEBUG_SUPPORT is enabled.  In addition, once it is
> > >> built, if you are using Debian version numbers, it will be helpfully
> > >> renamed to "libthread-db1" and the build will still fail.
> > >>
> > >>     
> > As pointed out earlier on this thread (and verified - there was some
> > confusion on my part since I didn't fully clean before rebuilding), the
> > library renaming itself doesn't cause any problems.  The only actual
> > problem is the lack of PTHREADS_DEBUG_SUPPORT.
> > > That's interesting as when I pushed these changes I did test with a
> > > uclibc target too.  What DISTRO/MACHINE are you using?
> > >   
> > I have a custom distro and machine, but broadly speaking it is
> > minimal-uclibc and ep93xx...
> 
> OK, that's what I was wondering.  Khem, do we think
> PTHREADS_DEBUG_SUPPORT should get enabled globally?  If so, then we
> should go and audit all of the distro uClibc.distro files and get this
> fixed for everybody.  Thanks.

yes I think it is needed for debugging threads so we have to enable it.
right we need to put it in all config files. I will take a look.

> 
> -- 
> Tom Rini
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel



      reply	other threads:[~2009-04-17 22:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-14 20:05 [PATCH] Supply uclibc-thread-db package expected by task-sdk-base David Huggins-Daines
2009-04-14 20:11 ` Koen Kooi
2009-04-16 16:29 ` Tom Rini
2009-04-16 17:00   ` David Huggins-Daines
2009-04-16 17:11     ` Tom Rini
2009-04-17 22:35       ` Khem Raj [this message]

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=20090417223550.GA15643@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=dhuggins@cs.cmu.edu \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.org \
    /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