From: Gary Thomas <gary@mlbassoc.com>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: Poky <poky@lists.pokylinux.org>
Subject: Re: Problems adding native support packages
Date: Fri, 11 Mar 2011 05:13:30 -0700 [thread overview]
Message-ID: <4D7A11EA.4050306@mlbassoc.com> (raw)
In-Reply-To: <4D7A052A.2050400@mlbassoc.com>
On 03/11/2011 04:19 AM, Gary Thomas wrote:
> On 03/10/2011 09:57 PM, Tian, Kevin wrote:
>>> From: Gary Thomas
>>> Sent: Friday, March 11, 2011 11:29 AM
>>>
>>> I'm trying to import a native package from OE for which the
>>> main package depends on libiconv. This seems to imply that
>>> when I extend to the native package using BBCLASSEXTEND, the
>>> native package depends on virtual/libiconv-native
>>>
>>> I can't figure out how to provide this. Any clues?
>>
>> I'm not sure about the problem here. do you want virtual/libiconv-native dependency
>> or not? If target recipe already has a DEPENDS = "libiconv", then with BBCLASSEXTEND
>> you have libiconv-native automatically.
>>
>> Or if you only want to add libiconv-native for native recipe exclusively, then:
>>
>> DEPENDS_virtclass-native = "virtual/libiconv-native"
>
> Actually, the problem is that such a dependency was added automatically by BBCLASSEXTEND.
> virtual/libiconv is provided by eglibc package, but it's not clear if it can provide
> virtual/libiconv-native
It comes from this dependency which seems very hard to satisfy:
meta/recipes-graphics/pango/pango.inc:DEPENDS = "glib-2.0 fontconfig freetype zlib virtual/libiconv virtual/libx11 libxft gtk-doc-native cairo"
It looks like I can side-step this by adding
ASSUME_PROVIDED += " virtual/libiconv-native "
>
> The other problem is that there is a meta/recipes-support/libiconv/libiconv_1.9.2.bb recipe
> in the tree which does not build at all, native or target.
>
>>>
>>> n.b. the recipe from OE is librsvg and importing it seems to be
>>> pretty invasive. To build the native package, I needed to add
>>> native support for all of these packages:
>>>
>>> # modified: meta/recipes-gnome/gnome/libart-lgpl_2.3.21.bb
>>> # modified: meta/recipes-gnome/gtk+/gtk+.inc
>>> # modified: meta/recipes-graphics/cairo/cairo.inc
>>> # modified: meta/recipes-graphics/pango/pango.inc
>>> # modified: meta/recipes-graphics/xorg-lib/libxcomposite_0.4.3.bb
>>> # modified: meta/recipes-graphics/xorg-lib/libxcursor_1.1.11.bb
>>> # modified: meta/recipes-graphics/xorg-lib/libxdamage_1.1.3.bb
>>> # modified: meta/recipes-graphics/xorg-lib/libxfixes_4.0.5.bb
>>> # modified: meta/recipes-graphics/xorg-lib/libxft_2.2.0.bb
>>> # modified: meta/recipes-graphics/xorg-lib/libxrandr_1.3.1.bb
>>> # modified: meta/recipes-graphics/xorg-lib/libxrender_0.9.6.bb
>>> # modified: meta/recipes-graphics/xorg-lib/pixman_0.20.2.bb
>>> # modified:
>>> meta/recipes-graphics/xorg-proto/compositeproto_0.4.2.bb
>>> # modified:
>>> meta/recipes-graphics/xorg-proto/damageproto_1.2.1.bb
>>> # modified: meta/recipes-graphics/xorg-proto/fixesproto_4.1.2.bb
>>> # modified: meta/recipes-graphics/xorg-proto/randrproto_1.3.2.bb
>>> # modified:
>>> meta/recipes-graphics/xorg-proto/renderproto_0.11.1.bb
>>> # modified:
>>> meta/recipes-graphics/xorg-proto/xineramaproto_1.2.1.bb
>>> # modified: meta/recipes-multimedia/alsa/alsa-tools_1.0.20.bb
>>> # modified: meta/recipes-support/atk/atk.inc
>>> # modified: meta/recipes-support/libcroco/libcroco_0.6.2.bb
>>> # modified: meta/recipes-support/libgcrypt/libgcrypt.inc
>>> # modified: meta/recipes-support/libgpg-error/libgpg-error_1.9.bb
>>>
>>> I also ran into a problem when I added native to atk, I get this error
>>> which makes no sense at all to me:
>>> NOTE: package atk-native-1.32.0-r0: task do_fetch: Started
>>> ERROR: Function 'Fetcher failure for URL:
>>> 'http://download.gnome.org/sources/atk/1.32/atk-native-1.32.0.tar.bz2'.
>>> Unable to fetch URL
>>> http://download.gnome.org/sources/atk/1.32/atk-native-1.32.0.tar.bz2 from
>>> any source.' failed
>>> This seems to be the only package in the set above that wants to fetch a
>>> -native
>>> tarball (there are no such files in the sources repository as far as I can tell)
>>>
>>> Thanks
>>>
>>>
>>> --
>>> ------------------------------------------------------------
>>> Gary Thomas | Consulting for the
>>> MLB Associates | Embedded world
>>> ------------------------------------------------------------
>>> _______________________________________________
>>> poky mailing list
>>> poky@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/poky
>
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2011-03-11 12:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 3:28 Problems adding native support packages Gary Thomas
2011-03-11 4:57 ` Tian, Kevin
2011-03-11 5:09 ` Xu, Dongxiao
2011-03-11 5:15 ` Tian, Kevin
2011-03-11 5:18 ` Xu, Dongxiao
2011-03-11 5:52 ` Tian, Kevin
2011-03-11 22:25 ` Richard Purdie
2011-03-13 22:26 ` Gary Thomas
2011-03-11 11:29 ` Gary Thomas
2011-03-11 8:21 ` Khem Raj
2011-03-11 11:19 ` Gary Thomas
2011-03-11 12:13 ` Gary Thomas [this message]
2011-03-11 16:23 ` Joshua Lock
2011-03-12 0:09 ` Tian, Kevin
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=4D7A11EA.4050306@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=kevin.tian@intel.com \
--cc=poky@lists.pokylinux.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