Summary: | app-emulation/emul-linux-x86-compat-20091004_rc1: Detected file collisions | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Pacho Ramos <pacho> |
Component: | Current packages | Assignee: | AMD64 Project <amd64> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | rauchwolke, toolchain |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 165270 |
Description
Pacho Ramos
2009-10-07 17:59:51 UTC
toolchain: Does sys-libs/libstdc++-v3 provide 32bit libs now? If so we need to add blockers on older versions of emul-linux-x86-compat and I need to update my package lists. Please advise. libstdc++-v3 really hasnt been touched in many many months, so people havent knowingly been adding functionality In all amd64 systems I have tried I get this collision because sys-libs/libstdc++-v3 *on multilib profiles* install that files. If I don't misremember, I think that I saw some change in multilib USE flag behavior months ago, maybe that was "hiding" this problem. Also, reading app-emulation/emul-linux-x86-compat description: emul-linux-x86 version of lib-compat, with the addition of a 32bit libgcc_s and the libstdc++ versions provided by gcc 3.3 and 3.4 for non-multilib systems. seems that those files are only needed for non-multilib systems This is solved in app-emulation/emul-linux-x86-compat-20091226 removing affected file on multilib profiles, as seems suggested by package description, that suggests that they are needed only in non-multilib systems. I have also tried on three amd64 multilib systems and, in all of them, those files are provided by sys-libs/libstdc++-v3-3.3.6 If you disagree with this solution, feel free to reopen the bug but, please, suggest a better one ;-) Best regards |