Red Hat Bugzilla – Bug 708531
fails to build without downstream patches
Last modified: 2017-12-06 05:39:47 EST
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. rpmbuild --define '__patch /bin/true' --rebuild gnome-system-monitor-2.28.0-7.el6.src.rpm
DEBUG: configure: WARNING: unrecognized options: --enable-selinux, --enable-polkit
DEBUG: Source code location: .
DEBUG: C Compiler: gcc
DEBUG: C++ Compiler: g++
DEBUG: CFLAGS: -Wall -Winline -Wchar-subscripts -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wc
DEBUG: CXXFLAGS: -Wall -std=c++98 -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=gene
DEBUG: Maintainer mode:
DEBUG: + make -C src gnome-system-monitor-mechanism-glue.h gnome-system-monitor-mechanism-client-glue.h
DEBUG: make: Entering directory `/builddir/build/BUILD/gnome-system-monitor-2.28.0/src'
DEBUG: make: Leaving directory `/builddir/build/BUILD/gnome-system-monitor-2.28.0/src'
DEBUG: make: *** No rule to make target `gnome-system-monitor-mechanism-glue.h'. Stop.
DEBUG: error: Bad exit status from /var/tmp/rpm-tmp.LpwG86 (%build)
DEBUG: Bad exit status from /var/tmp/rpm-tmp.LpwG86 (%build)
The proposed change is required for Coverity to scan defects in downstream
Created attachment 501401 [details]
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.
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.
The official life cycle policy can be reviewed here:
This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL: