From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] tclibc-eglibc: use glibc-thread-db as eglibc-thread-db does not exist(?)
Date: Tue, 12 Feb 2013 16:30:04 +0000 [thread overview]
Message-ID: <1360686604.30425.41.camel@ted> (raw)
In-Reply-To: <1360679147-24511-1-git-send-email-marcin.juszkiewicz@linaro.org>
On Tue, 2013-02-12 at 15:25 +0100, Marcin Juszkiewicz wrote:
> | Collected errors:
> | * satisfy_dependencies_for: Cannot satisfy the following dependencies for packagegroup-core-standalone-hhvm-sdk-target:
> | * eglibc-thread-db *
>
> eglibc-thread-db is listed in LIBC_DEPENDENCIES and used by SDK. Package
> ends as "libthread-db1" and provides glibc-thread-db.
>
> Signed-off-by: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
> ---
> meta/conf/distro/include/tclibc-eglibc.inc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Package renaming should take care of this. If it doesn't happen, that is
a bug in the package renaming. This just hacks around it.
How do we reproduce this?
Cheers,
Richard
> diff --git a/meta/conf/distro/include/tclibc-eglibc.inc b/meta/conf/distro/include/tclibc-eglibc.inc
> index 15f5ee5..88bfd40 100644
> --- a/meta/conf/distro/include/tclibc-eglibc.inc
> +++ b/meta/conf/distro/include/tclibc-eglibc.inc
> @@ -23,7 +23,7 @@ LIBC_DEPENDENCIES = "libsegfault \
> eglibc-dbg \
> eglibc-dev \
> eglibc-utils \
> - eglibc-thread-db \
> + glibc-thread-db \
> ${@get_libc_locales_dependencies(d)}"
>
> LIBC_LOCALE_DEPENDENCIES = "\
next prev parent reply other threads:[~2013-02-12 16:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 14:25 [PATCH] tclibc-eglibc: use glibc-thread-db as eglibc-thread-db does not exist(?) Marcin Juszkiewicz
2013-02-12 16:30 ` Richard Purdie [this message]
2013-02-12 16:54 ` Marcin Juszkiewicz
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=1360686604.30425.41.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=marcin.juszkiewicz@linaro.org \
--cc=openembedded-core@lists.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