| Summary: | dev-lang/i{f,c} remove core libraries if installed together | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Alexander Bezrukov <phmagic> |
| Component: | [OLD] Development | Assignee: | Andrey Kislyuk (RETIRED) <weaver> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | bicatali, kernel, nanikata15 |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | emerge --info | ||
Created attachment 213852 [details]
emerge --info
|
In order to avoid "unnecessary" installation of intel compiler suite core libraries, the said ebuilds use the following approach: if has_version "~dev-lang/ifc-${PV}"; then rm -f rpm/*cprolib*.rpm (if installing icc; ifc is changed to icc, if ifc is being installed). This means that if both packages once emerged, after re-emerge (e.g. because USE flags got changed) the libraries belonging to intel-cprolib* will be removed, rendering the compiler suite unusable. I believe that a reasonable solution would be to merge the icc and ifc ebuilds into one and select rpms based on USE flags (as it is already done with ipp and mkl). This would also solve the problem of inconsistent USE flags for different components (e.g. icc[+idb] and ifc[-idb]), which lead to a situation where availability of a component depends on the emerge order. Reproducible: Always Steps to Reproduce: 1. for i in 1 2; do emerge icc ifc; done 2. build a "Hello, world" program Actual Results: ld: cannot find -limf Expected Results: The program should compile and link successfully