| Summary: | [rpm] installation errors on powerpc | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Qing He <qing.he> |
| Component: | core | Assignee: | Mark Hatle <mark.hatle> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | High | CC: | liang.li2, meta.mr.watcher, meta.watcher |
| Version: | 1.0 | ||
| Target Milestone: | 1.0 M4 | ||
| Hardware: | x86 | ||
| OS: | ppc | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Qing He
2011-02-22 22:33:36 UTC
also happended on sato and sato-sdk images in nightly build 20110217-1 from http://autobuilder.pokylinux.org/nightly/20110217-1/qemu/qemuppc/ see below: root@qemuppc:~# rpm -ivh man-1.6f-r0.ppc603e.rpm warning: package man-1.6f-r0.ppc603e is intended for a ppc603e-pc-linux-gnu platform root@qemuppc:~# rpm -qa |grep man-1.6f root@qemuppc:~# Can you check what the /etc/rpm/platform file says? This file should be constructed based on the compatible CPUs mentioned by the Poky build environment. It's possible something isn't working correctly with the construction of this file. I'll attempt to build a qemuppc machine locally and see what I can reproduce. (In reply to comment #2) > Can you check what the /etc/rpm/platform file says? > This file should be constructed based on the compatible CPUs mentioned by the > Poky build environment. It's possible something isn't working correctly with > the construction of this file. > I'll attempt to build a qemuppc machine locally and see what I can reproduce. powerpc-unknown-linux all-unknown-linux any-unknown-linux noarch-unknown-linux powerpc-unknown-linux ppc603e-unknown-linux qemuppc-unknown-linux What I did is adding "ppc603e-pc-linux-gnu" in it and installation can continue. Btw, x86_64 images also observe this. Fixed with: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=08c8f7bb7375a6f51c12ee5e7808e38e914d5413 The problem was due to the platform file not being configured properly. |