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 1605559
| Summary: | pymol: FTBFS in Fedora rawhide | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mohan Boddu <mboddu> | ||||||||
| Component: | pymol | Assignee: | Tim Fenn <tim.fenn> | ||||||||
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | rawhide | CC: | dan, mhroncok, tim.fenn | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | pymol-2.1.0-3.20180321svn4187.fc29 | Doc Type: | If docs needed, set a value | ||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2018-08-06 12:34:44 UTC | Type: | --- | ||||||||
| 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: | 1551327, 1565020, 1602938 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Mohan Boddu
2018-07-20 16:00:19 UTC
Created attachment 1465853 [details]
build.log
Created attachment 1465854 [details]
root.log
file root.log too big, will only attach last 32768 bytes
Created attachment 1465855 [details]
state.log
OK, I fixed the immediate issue, yet there is a gcc-c++ build failure on ppc64le. https://koji.fedoraproject.org/koji/taskinfo?taskID=28564602 (In reply to Miro Hrončok from comment #4) > OK, I fixed the immediate issue, yet there is a gcc-c++ build failure on > ppc64le. > > https://koji.fedoraproject.org/koji/taskinfo?taskID=28564602 Yeah, this is where I've been stuck - the error isn't informative and I can't find a good ppc64le build system to test with? CCing Dan, he might have something for you to debug this on. (In reply to Tim Fenn from comment #5) > (In reply to Miro Hrončok from comment #4) > > OK, I fixed the immediate issue, yet there is a gcc-c++ build failure on > > ppc64le. > > > > https://koji.fedoraproject.org/koji/taskinfo?taskID=28564602 > > Yeah, this is where I've been stuck - the error isn't informative and I > can't find a good ppc64le build system to test with? all maintainers can use machines from https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintainers the problem looks like a real problem in pymol (or its bundled libs) (This is a mass bug update. Forgive me if things are not 100% accurate for this one.) At this moment, your package still requires Python 3.6. This will cause broken upgrades to Fedora 29. Please prioritize this rebuild. Let me know if you need help from the Python maintenance team figuring out why the package FTBFS. Consider orphaning the package if you don't have time for it. Consider retiring the package if upstream is dead and nothing depends on it in Fedora. If you are blocked by other packages (I've recently tried to set the Bugzilla metadata to reflect that), consider helping there as well. Thank you. Igor, this has been unblocked in comment #4. This is another friendly reminder. Please take action. The problem is with the -std=c++0x compiler option. It causes the "unix" preprocessor symbol to be undefined which is them missing in <msgpack/v1/vrefbuffer.hpp> to include <sys/uio.h> that defines "struct iovec". For the record pymol is FTBFS in F-28 too. -std=c++11 doesn't help either (In reply to Miro Hrončok from comment #12) > -std=c++11 doesn't help either -std=gnu++0x/gnu++11 helps, feel free to revert my workaround Thanks Dan. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |