Patchwork [0/2] Populate site config files content to rootfs

login
register
mail settings
Submitter Lianhao Lu
Date Aug. 11, 2011, 2:31 p.m.
Message ID <cover.1313072334.git.lianhao.lu@intel.com>
Download mbox
Permalink /patch/9601/
State New, archived
Headers show

Pull-request

git://git.yoctoproject.org/poky-contrib llu/bug892

Comments

Lianhao Lu - Aug. 11, 2011, 2:31 p.m.
This series of patches fixed the bug #892. Currently, the site config 
files used in the cross compiling environment generated by meta-toolchain 
partly come from SITECONFIG_SYSROOT_CACHE, where each package will put 
their own site config cache file during their populate-sysroot task.

However, there is no way to guarantee the meta-toolchain to collect these 
site config cache files after all other packages have finished their 
populate-sysroot tasks. Since we now encourage users to use the same rootfs 
for both running and cross-compiling, by populating the site config files'
content into rootfs and having the CONFIG_SITE pointing to the rootfs, we 
can gurantee the cross compiling environment not missing any site config 
cache files' content.

The following changes since commit a1f87ec65fa1a6d5ce9a010548dbe7c01ab9b711:
  Kumar Gala (1):
        eglibc: force GLIBC_EXTRA_OECONF to not be uset for nativesdk

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib llu/bug892
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=llu/bug892

Lianhao Lu (2):
  image: populate site config files into roootfs.
  meta-toolchain/environment: Use site config in rootfs.

 meta/classes/image.bbclass                 |    1 +
 meta/classes/populate_sdk.bbclass          |    2 +-
 meta/classes/siteinfo.bbclass              |    4 +++-
 meta/classes/toolchain-scripts.bbclass     |   26 ++++++++++++++++++++------
 meta/recipes-core/meta/meta-environment.bb |    6 +-----
 meta/recipes-core/meta/meta-toolchain.bb   |    4 +---
 6 files changed, 27 insertions(+), 16 deletions(-)
Richard Purdie - Aug. 15, 2011, noon
On Thu, 2011-08-11 at 22:31 +0800, Lianhao Lu wrote:
> This series of patches fixed the bug #892. Currently, the site config 
> files used in the cross compiling environment generated by meta-toolchain 
> partly come from SITECONFIG_SYSROOT_CACHE, where each package will put 
> their own site config cache file during their populate-sysroot task.
> 
> However, there is no way to guarantee the meta-toolchain to collect these 
> site config cache files after all other packages have finished their 
> populate-sysroot tasks. Since we now encourage users to use the same rootfs 
> for both running and cross-compiling, by populating the site config files'
> content into rootfs and having the CONFIG_SITE pointing to the rootfs, we 
> can gurantee the cross compiling environment not missing any site config 
> cache files' content.

I'm afraid I'm not very keen on this patch since it complicates the
situation and I'm not sure its an improvement. We strive very hard never
to add files to a rootfs which aren't packaged and this approach breaks
that (and always adds them to certain image types which again, I worry
about).

Can't we use the no_cache option to siteinfo_get_files() to address this
bug, yet leave the cache files where they are currently located as part
of the toolchain?

Ultimately we could specific extra cache files to add (such as eglibc)
and ensure we have the correct dependencies to ensure the caches are
generated.

Cheers,

Richard