| Summary: | source rpm building error | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Dave Johnson <dajohnso> |
| Component: | mingw32-boost | Assignee: | Kai Tietz <ktietz> |
| Status: | CLOSED WONTFIX | QA Contact: | IDM QE LIST <seceng-idm-qe-list> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.2 | CC: | lockhart, mnewsome |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-09-18 10:36:10 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Dave Johnson
2011-09-21 15:15:10 UTC
Email from John W. Lockhart <lockhart>: I'm not sure what your status on it is, but I tried the following last night, and it rebuilt just fine: .qa.[root@x86-64-6cn-v1 tps.2]# rpm -e --nodeps doxygen graphviz libxslt mpich2-devel .qa.[root@x86-64-6cn-v1 tps.2]# rpmbuild --rebuild --define "dist .el6" --define '_topdir /usr/src/redhat' --rcfile /tmp/tps_rpmrc_jzWziJ:/usr/lib/rpm/rpmrc:/usr/lib/rpm/redhat/rpmrc /mnt/redhat/brewroot/packages/mingw32-boost/1.41.0/3.el6/src/mingw32-boost-1.41.0-3.el6.src.rpm 2>&1 | tee Rebuild-boost.log .qa.[root@x86-64-6cn-v1 tps.2]# yum -y install doxygen graphviz libxslt mpich2-devel Logs and such are in: /mnt/qa/scratch/x86-64-6cn-v1/2011:11790/tps.2/ This means that there's a bug in the mingw32-boost .spec file, or configuration routines in the build. If those 4 packages are installed (or perhaps a subset of them; I didn't test all the combos), the build tries to use things that it can't handle. The fix is to explicitly disable the unhandled features -- e.g., instead of stuff like "use doxygen? [auto]" or whatever, set the answer to '[no]'. How serious it is, and whether to fix it -- that's another story. :) Tends to be useful to have fixed, but it depends on priority, how many other fixes need work, etc. -- John Since RHEL 6.2 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. |