From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] xlib_libpthread-stubs: needs thread support
Date: Tue, 8 Oct 2013 23:51:46 +0200 [thread overview]
Message-ID: <20131008235146.63b90c26@skate> (raw)
In-Reply-To: <1381267637-3957-1-git-send-email-jerzy.grzegorek@trzebnica.net>
Dear Jerzy Grzegorek,
On Tue, 8 Oct 2013 23:27:17 +0200, Jerzy Grzegorek wrote:
> config BR2_PACKAGE_XLIB_LIBPTHREAD_STUBS
> bool "libpthread-stubs"
> + depends on BR2_TOOLCHAIN_HAS_THREADS
No, that doesn't work. When you add a toolchain dependency to one
package, you must propagate it to the reverse dependencies of this
package that are selecting this package.
For example, libdrm and libxcb are both selecting
XLIB_LIBPTHREAD_STUBS, but they do not have the
BR2_TOOLCHAIN_HAS_THREADS, so you should add this dependency to libdrm
and libxcb as well.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-08 21:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 21:27 [Buildroot] [PATCH 1/1] xlib_libpthread-stubs: needs thread support Jerzy Grzegorek
2013-10-08 21:51 ` Thomas Petazzoni [this message]
2013-10-08 21:59 ` Jerzy Grzegorek
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=20131008235146.63b90c26@skate \
--to=thomas.petazzoni@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox