Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Running TPS tests and hitting this error.
http://nest.test.redhat.com/mnt/qa/scratch/x86-64-6cn-v1/2011:11790/tps/tps-srpmtest.log
--- REBUILD: mingw32-boost-1.41.0-3.el6.src.rpm for noarch ---------------------
begin at 09/21/2011 10:50:34 on x86-64-6cn-v1.ss.eng.bos.redhat.com
doRpmCommand: rpmbuild --rebuild --define "dist .el6" --define '_topdir /usr/src/redhat' --rcfile /tmp/tps_rpmrc_jgUTJj:/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
doRpmCommand-result (256):
FAILED to rebuild /mnt/redhat/brewroot/packages/mingw32-boost/1.41.0/3.el6/src/mingw32-boost-1.41.0-3.el6.src.rpm -- return code 256
REBUILD: FAIL for mingw32-boost-1.41.0-3.el6.src.rpmBUILDLOG: mingw32-boost-1.41.0-3.el6.src.rpm-noarch-rebuild.log contains full details. Reports from make and rpmbuild, with line numbers:
448---
449---
450--- [1;30mBUILD_TOOLS is NONE: skipping tools.[0m
451---
452--- Configuring incomplete, errors occurred!
453:error: Bad exit status from /var/tmp/rpm-tmp.cH9RXf (%build)
454-
455-
456-RPM build errors:
457- Bad exit status from /var/tmp/rpm-tmp.cH9RXf (%build)
Last 20 lines of Build Log:
-- + program_options
-- + rational
-- + signals
-- + signals2
-- + statechart
-- + tr1
-- + units
-- + wave
--
-- [1;30mBUILD_TESTS is NONE: skipping test directories.[0m
--
--
-- [1;30mBUILD_TOOLS is NONE: skipping tools.[0m
--
-- Configuring incomplete, errors occurred!
error: Bad exit status from /var/tmp/rpm-tmp.cH9RXf (%build)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.cH9RXf (%build)
===============
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
Comment 3RHEL Program Management
2011-10-07 15:56:43 UTC
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.