Bug 687917 - FTBFS - conflict with compat-gcc-34-g77
Summary: FTBFS - conflict with compat-gcc-34-g77
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: numpy
Version: 6.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Stanislav Ochotnicky
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-15 17:45 UTC by Zenon Panoussis
Modified: 2012-06-12 15:44 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-12 15:44:18 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Zenon Panoussis 2011-03-15 17:45:56 UTC
Building the SRPM ends prematurely with

extracting debug info from /root/rpmbuild/BUILDROOT/numpy-1.3.0-6.2.el6.x86_64/usr/lib64/python2.6/site-packages/numpy/linalg/lapack_lite.so
*** ERROR: No build ID note found in /root/rpmbuild/BUILDROOT/numpy-1.3.0-6.2.el6.x86_64/usr/lib64/python2.6/site-packages/numpy/linalg/lapack_lite.so
error: Bad exit status from /var/tmp/rpm-tmp.owJD7X (%install)

See bug #432194. The problem is still the same and the fix is still the same. I am unable to find the underlying cause, but at least a BuildConflicts: compat-gcc-34-g77 would prevent this from happening.

Comment 2 RHEL Program Management 2011-03-15 18:08:14 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. 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. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 3 Stanislav Ochotnicky 2012-06-12 15:44:18 UTC
I am closing this bug in the same way as the original bug was closed (WONTFIX). There is a simple workaround, preferred way to build RPMs is by using mock environment and there the bug doesn't appear either.

If you feel strongly about the issue feel free to contact your support representative.


Note You need to log in before you can comment on or make changes to this bug.