| Summary: | libmpfr4 clash when installing gdb cross ipk | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Meta-yocto | Reporter: | liping Ke <liping.ke> |
| Component: | meta-yocto | Assignee: | Qing He <qing.he> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | jessica.zhang, ke.yu, kevin.tian, lianhao.lu, poky.bs.watcher, poky.watcher, qing.he, richard.purdie, sgw |
| Version: | 1.0 | ||
| Target Milestone: | 1.0 M4 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
liping Ke
2010-11-25 00:15:16 UTC
Liping, could you please add reproduce step? /usr/share/info/dir is a collective file to include the entry points of all info pages i.e., when installing, /usr/share/info/dir should always be updated instead of overridden, such overriding generates errors like above. We should have a postinst in every -doc package to invoke something like install-info to update the dir file. One interesting thing is that, if I don't use sudo to install the opkg package to the /opt/poky but to some normal folders such as /home/lke/opt/poky, I can install. Seems the problem could be avoided. Yet I am not clear why this happens. If you want to repeat the process, please download the suitable conf file from http://llu-piketon.sh.intel.com, and run below command with your host opkg: opkg-cl -f /home/lke/opkg-sdk-i586.conf -o /home/lke/Downloads/testfolder update opkg-cl -f /home/lke/opkg-sdk-i586.conf -o /home/lke/Downloads/testfolder install gcc-cross-canadian Thanks & Regards, criping Interestingly, dpkg doesn't use -postinst for this specific requirement, the mechanism is called `trigger', it triggers on every /usr/share/info update, so no postinst is needed. Seems opkg doesn't have this mechanism, not sure about rpm. *** Bug 546 has been marked as a duplicate of this bug. *** Liping, Do we still see this problem? I will re-verify it this week. I guess no one has fixed it. I still use -f now I did not meet this problem any more. I will close this bug. |