From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: packaging errors in some -nativesdk recipes
Date: Wed, 21 Mar 2012 09:55:59 +0000 [thread overview]
Message-ID: <1332323759.9740.126.camel@ted> (raw)
In-Reply-To: <857BE142E5399E46B20FD45B9DB8A7BC0FD0349C@SHSMSX102.ccr.corp.intel.com>
On Wed, 2012-03-21 at 04:45 +0000, Lu, Lianhao wrote:
> When I'm looking at some package warnings of eglibc-nativesdk(and some
> other -nativesdk packages' warnings), e.g.
>
> WARNING: For recipe eglibc-nativesdk, the following files/directories
> were installed but not shipped in any package:
> WARNING: /opt/poky/1.1
> +snapshot/sysroots/x86_64-pokysdk-linux/lib/libthread_db.so.1
> WARNING: /opt/poky/1.1
> +snapshot/sysroots/x86_64-pokysdk-linux/lib/libnss_hesiod-2.13.so
> WARNING: /opt/poky/1.1
> +snapshot/sysroots/x86_64-pokysdk-linux/lib/libSegFault.so
> ...... ......
>
> I found this has something to do with the usage of PKGSUFFIX in
> eglibc-package.inc:
>
> PKGSUFFIX = ""
> PKGSUFFIX_virtclass-nativesdk = "-nativesdk"
> FILES_eglibc-thread-db${PKGSUFFIX} = "${base_libdir}/libthread_db.so.*
> ${base_libdir}/libthread_db-*.so"
>
> Instead of the variable FILES_eglibc-thread-db-nativesdk being
> defined, the variable FILES_eglibc-thread-db gets defined after
> parsing the eglib-nativesdk recipe, so many files are not packaged in
> relevant -nativesdk packages. This is because in the functioin
> finalize() of ast.py in bitbake, it first calls expandKeys() then
> update_data(), while the OVERRIDES only takes place in the function of
> update_data().
>
> I saw in the git history there was a commit to fix this issue at
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/meta/recipes-core/eglibc/eglibc-package.inc?id=f800862555b81dec65f3de09a2f7b1a0c97a09c1, but later was reverted by the commit http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/meta/recipes-core/eglibc/eglibc-package.inc?id=2a7870778f141b2f29271405ee62b06cc4856920.
>
> Any suggestions of how to resolve this issue? We're not 100% sure if
> we can change the sequence of calling expandKeys() and update_data()
> in the finalize() in ast.py in bitbake without causing any other
> problems.
We can't change that order, it would create many problems.
How about setting PKGSUFFIX = "-nativesdk" directly in
nativesdk.bbclass?
Cheers,
Richard
prev parent reply other threads:[~2012-03-21 10:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 4:45 packaging errors in some -nativesdk recipes Lu, Lianhao
2012-03-21 9:55 ` Richard Purdie [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=1332323759.9740.126.camel@ted \
--to=richard.purdie@linuxfoundation.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 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.