All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hongxu Jia <hongxu.jia@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Cc: saul.wold@intel.com
Subject: Re: [PATCH 1/1] libpthread-stubs: add ALLOW_EMPTY_${PN} = "1"
Date: Tue, 19 Nov 2013 10:20:20 +0800	[thread overview]
Message-ID: <528ACAE4.1060901@windriver.com> (raw)
In-Reply-To: <4e295b4e41dca18db1acab845627396eddb39633.1384827264.git.hongxu.jia@windriver.com>

On 11/19/2013 10:15 AM, Hongxu Jia wrote:
> There was an image build failure while installing libpthread-stubs to rootfs.
> ...
> Failed to buld rootfs image for fsl-b4xxx-standard-glibc-std after adding
> multilib package lib64-libpthread-stubs.
> ...
>
> The libpthread-stubs was empty and the package didn't exist by default. Add
> ALLOW_EMPTY_${PN} = "1" to create the empty libpthread-stubs fixed this issue.

In libpthread-stubs recipe, the PN-dbg and PN-dev existed,
so the PN should also exist.

//Hongxu

>
> Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
> ---
>   meta/recipes-graphics/xcb/libpthread-stubs_0.3.bb | 1 +
>   1 file changed, 1 insertion(+)
>
> diff --git a/meta/recipes-graphics/xcb/libpthread-stubs_0.3.bb b/meta/recipes-graphics/xcb/libpthread-stubs_0.3.bb
> index ad046d1..f4264b4 100644
> --- a/meta/recipes-graphics/xcb/libpthread-stubs_0.3.bb
> +++ b/meta/recipes-graphics/xcb/libpthread-stubs_0.3.bb
> @@ -22,3 +22,4 @@ RDEPENDS_${PN}-dev = ""
>   RRECOMMENDS_${PN}-dbg = "${PN}-dev (= ${EXTENDPKGV})"
>   
>   BBCLASSEXTEND = "native nativesdk"
> +ALLOW_EMPTY_${PN} = "1"



      reply	other threads:[~2013-11-19  2:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-19  2:15 [PATCH 0/1] libpthread-stubs: add ALLOW_EMPTY_${PN} = "1" Hongxu Jia
2013-11-19  2:15 ` [PATCH 1/1] " Hongxu Jia
2013-11-19  2:20   ` Hongxu Jia [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=528ACAE4.1060901@windriver.com \
    --to=hongxu.jia@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=saul.wold@intel.com \
    /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.