public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Robert Yang <liezhi.yang@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/3] liberation-fonts: can't be allarch
Date: Thu, 7 Jan 2016 12:11:20 +0100	[thread overview]
Message-ID: <20160107111120.GC2512@jama> (raw)
In-Reply-To: <228ce5dac7d96467f7165add45a39cfcd12c7bfc.1452152689.git.liezhi.yang@windriver.com>

[-- Attachment #1: Type: text/plain, Size: 1767 bytes --]

On Wed, Jan 06, 2016 at 11:45:24PM -0800, Robert Yang wrote:
> liberation-fonts inherit fontcache which would depend on fontconfig, and
> fontconfig is not allarch, so that liberation-fonts can't be allarch.
> 
> It caused a problem:
> $ bitbake lib32-core-image-sato
> 
> Both lib32-fontconfig and fontconfig would be built, but fontconfig
> shouldn't, this patch can fix the problem.
> 
> [YOCTO #8882]

liberation-fonts excludes fontconfig dependency since:
commit 0b5e868d160faca041cda42b670066facd4db531
Author: Richard Purdie <richard.purdie@linuxfoundation.org>
Date:   Tue Aug 25 17:58:12 2015 +0100

    layer.conf: Add several allarch dependency exclusions

If it doesn't work then you probably should remove the entry from
layer.conf as well.

> 
> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
> ---
>  .../ttf-fonts/liberation-fonts_1.04.bb             |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta/recipes-graphics/ttf-fonts/liberation-fonts_1.04.bb b/meta/recipes-graphics/ttf-fonts/liberation-fonts_1.04.bb
> index bda82e7..f64748c 100644
> --- a/meta/recipes-graphics/ttf-fonts/liberation-fonts_1.04.bb
> +++ b/meta/recipes-graphics/ttf-fonts/liberation-fonts_1.04.bb
> @@ -13,7 +13,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f"
>  PR = "r4"
>  PE = "1"
>  
> -inherit allarch fontcache
> +inherit fontcache
>  
>  FONT_PACKAGES = "${PN}"
>  
> -- 
> 1.7.9.5
> 
> -- 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2016-01-07 11:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-07  7:45 [PATCH 0/3] meta: 3 fixes Robert Yang
2016-01-07  7:45 ` [PATCH 1/3] cogl-1.0: fix may be used uninitialized error Robert Yang
2016-01-07  7:45 ` [PATCH 2/3] run-postinsts: can't be allarch Robert Yang
2016-01-07 10:57   ` Richard Purdie
2016-01-08  6:03     ` Robert Yang
2016-01-11  8:27     ` Robert Yang
2016-01-19  9:22     ` Robert Yang
2016-01-07  7:45 ` [PATCH 3/3] liberation-fonts: " Robert Yang
2016-01-07 11:11   ` Martin Jansa [this message]
2016-01-07 12:16   ` Phil Blundell
2016-01-07 12:55     ` Martin Jansa
2016-01-13  5:56       ` Robert Yang
2016-01-13  6:00         ` Robert Yang

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=20160107111120.GC2512@jama \
    --to=martin.jansa@gmail.com \
    --cc=liezhi.yang@windriver.com \
    --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