| Summary: | Generate locales at build time to speed up first boot | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Meta-yocto | Reporter: | Jiajun Xu <jiajun.xu> |
| Component: | meta-yocto | Assignee: | Nitin Kamble <nitin.a.kamble> |
| Status: | VERIFIED NOTABUG | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Low | CC: | jessica.zhang, josh, kevin.tian, poky.bs.watcher, poky.watcher, richard.purdie, sgw, susie.li, xianchao.zhang, yongkang.you |
| Version: | 0.9 | ||
| Target Milestone: | 0.9 M4 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Program Management | Documentation change: | --- |
|
Description
Jiajun Xu
2010-07-26 07:29:31 UTC
build time Locale generation is enabled in the poky. please verify the issue is not present now. (In reply to comment #1) > build time Locale generation is enabled in the poky. > please verify the issue is not present now. Nitin, Is the patch in milestone branch? Is it OK for us to verify the issue against M3 build image? BTW, if a bug is fixed and fixing patch is built in our weekly/nightly build, you can mark the bug status as "RESOLVED FIXED" then. the build/milestone branch is still set tu use glibc instead of eglibc. eglibc generates many locales while glibc is is configured to build just few locales. for both build time locale generation is enabled by this commit. so to answer your question, It is ok for you to verify the issue against M3 build image, as I hear from Saul builds/milestone branch is same as M3. http://git.pokylinux.org/cgit/cgit.cgi/poky-contrib/commit/?h=builds/milestone&id=561d875404ef1783f94f37314b6e756766db8411 author Nitin A Kamble <nitin.a.kamble@intel.com> 2010-08-06 02:38:06 (GMT) committer Richard Purdie <rpurdie@linux.intel.com> 2010-09-02 08:52:31 (GMT) commit 561d875404ef1783f94f37314b6e756766db8411 (patch) (side-by-side diff) tree 664f8afe01c9ba8828ab02b19367e97e52dae842 parent 436d590c4a5b7b5942bac5b51af128bcdd30621f (diff) download poky-contrib-561d875404ef1783f94f37314b6e756766db8411.zip poky-contrib-561d875404ef1783f94f37314b6e756766db8411.tar.gz poky-contrib-561d875404ef1783f94f37314b6e756766db8411.tar.bz2 libc-package.bbclass: merge glibc & eglibc class files Other enhancements: print qemu's stdio & error on failure glibc: enable locale generation for all arches eglibc: enable binary locale generation for mips And cleanup of code based on the code review. [e]glibc: move common definition in the common file. bitbake was complaining about duplicate definition of get_libc_fpu_setting in eglibc.inc & glibc.inc files. And bump PRs Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com> Xianchao, Pls. verify if the bug exist with latest image. The issue is that the first time you download and boot the qemuppc sato/sdk image, the booting time will take more than 5 minutes. (In reply to comment #4) > Xianchao, > Pls. verify if the bug exist with latest image. The issue is that the first > time you download and boot the qemuppc sato/sdk image, the booting time will > take more than 5 minutes. With the latest build image (20101007), the first boot time need about 4-5 minutes. (In reply to comment #5) > (In reply to comment #4) > > Xianchao, > > Pls. verify if the bug exist with latest image. The issue is that the first > > time you download and boot the qemuppc sato/sdk image, the booting time will > > take more than 5 minutes. > With the latest build image (20101007), the first boot time need about 4-5 > minutes. I check with 20101018 build, it still needs about 4 mintues to boot up qemuppc image. Reopen the bug. (In reply to comment #6) > > I check with 20101018 build, it still needs about 4 mintues to boot up qemuppc > image. Reopen the bug. It's only mentioned that it takes 4 minutes to boot up. Can you look what is happening in that 4 minutes? I do not see any data that shows that the 4 minutes boottime is caused for locale generation. possibly it is doing fsck. please verify what is happening. (In reply to comment #8) > possibly it is doing fsck. please verify what is happening. qemuppc will wait for a long time after printing following message and give me a login prompt. ######### md: Waiting for all devices to be available before autodetect md: If you don't use raid, use raid=noautodetect md: Autodetecting RAID arrays. md: Scanned 0 and added 0 devices. md: autorun ... md: ... autorun DONE. EXT3-fs (hda): warning: feature flags set on rev 0 fs, running e2fsck is recommended EXT3-fs (hda): mounted filesystem with writeback data mode VFS: Mounted root (ext3 filesystem) readonly on device 3:0. Freeing unused kernel memory: 180k init kjournald starting. Commit interval 5 seconds EXT3-fs (hda): warning: updating to rev 1 because of new feature flag, running e2fsck is recommended EXT3-fs (hda): using internal journal ######### (In reply to comment #9) So it is not busy generating locales. maybe you can open another bug for boot speed issue. OK. Let me open another bug. |