Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 893294
Summary: | ARM: error while loading shared libraries: libLLVM-3.1.so: cannot open shared object file: No such file or directory | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jens Petersen <petersen> |
Component: | llvm | Assignee: | Jens Petersen <petersen> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | bos, codonell, dmalcolm, jakub, law, michel, pbrobinson, pfrankli, schwab, scottt.tw, spoyarek |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | arm | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | llvm-3.1-13.fc19 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-01-24 02:05:55 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: | 245418 |
Description
Jens Petersen
2013-01-09 04:02:39 UTC
I am still wondering if this is llvm specific or a ld.conf glibc ARM issue. I wanted to try to test tix for example but right now F19 ARM is broken (policycoreutils version conflict with selinux-policy). (In reply to comment #2) > I wanted to try to test tix for example but right now F19 ARM is broken > (policycoreutils version conflict with selinux-policy). Should now be fixed, I actually fixed it yesterday but we've a severe lack of newRepo hosts so it's taking a while bconoboy suggested this issue was a temporarily toolchain problem at the time and probably fixed now if ones rebuilds. So I went ahead and bumped now to llvm-3.1-13.fc19. http://koji.fedoraproject.org/koji/taskinfo?taskID=4895310 http://arm.koji.fedoraproject.org/koji/taskinfo?taskID=1381294 <bconoboy> Well, it happened with mysql, and one other library (don't remember which) Anyway likely this is already fixed in F19 Rawhide but reassigning to glibc which provides ldconfig just for reference and completeness. Will update here after testing the new build on ARM tomorrow. Further note this is purely an F19 issue so I don't think it should be on the F18ARMBLocker list. Peter? > http://koji.fedoraproject.org/koji/taskinfo?taskID=4895310 This failed to complete due to some old pod markup problems, which the new perl-Pod-Parser seems more strict about. Should be fixed in: http://koji.fedoraproject.org/koji/taskinfo?taskID=4895618 http://arm.koji.fedoraproject.org/koji/taskinfo?taskID=1381686 I wanted clarification that this isn't an issue in F18 too Okay armv5tel build is still in progress but I confirmed that this issue is fixed with llvm-3.1-13.fc19.armv7hl on armv7hl f19 rawhide. (Note again for F18 Blocker people this issue does not affect F18.) (In reply to comment #9) > I wanted clarification that this isn't an issue in F18 too Ok thanks. I believe this ARM problem has never been seen on F18 only on F19 Rawhide. And it is not occurring for current F18 so it seems safe to remove F18ARMBlocker. Discussion earlier today UTC (last night US EST) on #fedora-arm: <bconoboy> We've run into a handful of packages where the library was stored under /usr/lib/somedir/library.so and it couldn't be found. Rebuilding the package solved the problem. : <bconoboy> My assumption is that the package was built under some faulty dependency <juhp> pbrobinson also recommended same : <bconoboy> Well, it happened with mysql, and one other library (don't remember which) : <juhp> only for rawhide? <bconoboy> haven't seen it on fc18 <juhp> aha <bconoboy> the fact that it works now suggests to me that whatever it was happened during an intermediate build version <juhp> ah okay so it might be fixed already? <bconoboy> believe so Above build seems also to corroborate this. http://arm.koji.fedoraproject.org/koji/buildinfo?buildID=108968 is the completed build of llvm-3.1-13.fc19. Just to confirm I tested f18 llvm by hand now and indeed this problem is not seen. As expected, since we have not been seeing it at all in f18 koji either. ghc is building now finally for f19 arm. (moved component back to llvm since the toolchain problem that caused this bug seems to have been long fixed and it is not clear anyway which component it was (binutils?)) |