Bug 1158661
Summary: | please consider upgrading to llvm-3.5.0 for f21 too | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Fabrice Bellet <fabrice> |
Component: | llvm | Assignee: | Adam Jackson <ajax> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 21 | CC: | ajax, bos, dmalcolm, jistone, jv+fedora, maxim.prohorenko, mjwolf, nouveau, petersen, scottt.tw, zboszor |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-12-02 04:36:04 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1051573 |
Description
Fabrice Bellet
2014-10-29 20:02:13 UTC
Hmm, llvm-3.5 seems to break ghc 7.6.3 badly on armv7hl (ie in Rawhide). So I would prefer to wait with llvm-3.5 f21 until that is sorted out. We are also in the F21 post-Beta phase now so it is rather late for such a major version bump. llvm34 is now available in rawhide and working with ghc on arm. *** Bug 1123103 has been marked as a duplicate of this bug. *** # yum --enablerepo="updates-testing" upgrade "llvm*" "mesa*" ... Transaction check error: file /usr/share/llvm/cmake/LLVMConfig.cmake conflicts between attempted installs of llvm-devel-3.5.0-4.fc21.i686 and llvm-devel-3.5.0-4.fc21.x86_64 I got the same multilib conflict: $ rpm -q llvm-devel llvm-devel-3.4-15.fc21.x86_64 llvm-devel-3.4-15.fc21.i686 $ yum update [...] Transaction check error: file /usr/share/llvm/cmake/LLVMConfig.cmake conflicts between attempted installs of llvm-devel-3.5.0-5.fc21.i686 and llvm-devel-3.5.0-5.fc21.x86_64 Note this is live in updates, not just updates-testing any more. As a workaround, it's fine for me to just remove llvm-devel.i686 for now... This multilib problem still exists today: file /usr/share/llvm/cmake/LLVMConfig.cmake conflicts between attempted installs of llvm-devel-3.5.0-6.fc21.i686 and llvm-devel-3.5.0-6.fc21.x86_64 As a Mesa developer, I need both packages to test changes with a variety of (32-bit and 64-bit, closed source and open souce) games and test suites. This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |