| Summary: | mklibs: Can't handle multilib paths | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Other YP Layers | Reporter: | Mark Hatle <mark.hatle> |
| Component: | layers | Assignee: | Constantin Musca <constantinx.musca> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | alexandru.damian, jessica.zhang, meta.layer.watcher, meta.watcher, sgw, song.liu |
| Version: | unspecified | ||
| Target Milestone: | 1.3 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | d6ef548c48968d16f7e24dec7452ddb455c26d46 | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Mark Hatle
2012-05-29 19:51:37 UTC
Testing config: local.conf: MULTILIBS = "" require conf/multilib.conf MKLIBS_OPTIMIZED_IMAGES ?= "all" MACHINE: qemux86-64 Everything seems fine (no error). Can you give me more details? Constantin perhaps this has been fixed? The issue (when first reported) was that '/lib' was hard coded into the mklibs. If you built an architecture that didn't have a /lib, or the libraries were not in /lib, you would either get a large number of warnings/errors (non-fatal) in the rootfs log... or you would end up with a python failure (fatal). The end result was that the target filesystem, if it completed, would not actually be prelinked. in the last comment I meant library optimized, NOT prelinked. Sorry. This bug has been fixed. commit d6ef548c48968d16f7e24dec7452ddb455c26d46 Author: Jesse Zhang <sen.zhang@windriver.com> Date: Tue Aug 7 10:31:57 2012 +0800 image-mklibs: pass correct libdir to mklibs libdir should be specified, or else mklibs won't work for 64bit targets. It wouldn't be able to find the libs. ... Cheers, Constantin |