Bug 1600429

Summary: flex FTBFS in rhel-7.6
Product: Red Hat Enterprise Linux 7 Reporter: Edjunior Barbosa Machado <emachado>
Component: flexAssignee: Patsy Griffin <pfrankli>
Status: CLOSED ERRATA QA Contact: Edjunior Barbosa Machado <emachado>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.6CC: law
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: flex-2.5.37-6.el7 Doc Type: No Doc Update
Doc Text:
undefined
 Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-30 10:13:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
flex-2.5.37-5.el7.src.rpm rebuild log in rhel-7.6 x86_64 none

Description Edjunior Barbosa Machado 2018-07-12 08:40:40 UTC 
Created attachment 1458284 [details]
flex-2.5.37-5.el7.src.rpm rebuild log in rhel-7.6 x86_64

Description of problem:
flex-2.5.37-5.el7 fails to build from srpm in rhel-7.6.

Like bug #1600084, adding gcc-c++ to BuildRequires solves this issue.

Version-Release number of selected component (if applicable):
flex-2.5.37-5.el7.src.rpm

How reproducible:
100%

Steps to Reproduce:
1. yum-builddep flex-2.5.37-5.el7.src.rpm -y
2. rpmbuild --rebuild flex-2.5.37-5.el7.src.rpm

Actual results:
(...)
Executing test test-c-cpp-nr
Test test-c-cpp-nr FAILED. See test-c-cpp-nr/OUTPUT for details.
Executing test test-c-cpp-r
Test test-c-cpp-r FAILED. See test-c-cpp-r/OUTPUT for details.
Executing test test-include-by-buffer
Test test-include-by-buffer succeeded.
Executing test test-include-by-push
Test test-include-by-push succeeded.
Executing test test-include-by-reentrant
Test test-include-by-reentrant succeeded.
Executing test test-prefix-nr
Test test-prefix-nr succeeded.
Executing test test-prefix-r
Test test-prefix-r succeeded.
Executing test test-pthread
Test test-pthread succeeded.
Executing test test-string-nr
Test test-string-nr succeeded.
Executing test test-string-r
Test test-string-r succeeded.
Executing test test-yyextra
Test test-yyextra succeeded.
Executing test test-alloc-extra
Test test-alloc-extra succeeded.
Executing test test-noansi-nr
Test test-noansi-nr succeeded.
Executing test test-noansi-r
Test test-noansi-r succeeded.
Executing test test-top
Test test-top succeeded.
Executing test test-table-opts
Test test-table-opts succeeded.
Results:
Tests succeeded: 41
Tests FAILED: 5
make[4]: *** [check-local] Error 1
make[4]: Leaving directory `/root/rpmbuild/BUILD/flex-2.5.37/tests'
make[3]: *** [check-am] Error 2
make[3]: Leaving directory `/root/rpmbuild/BUILD/flex-2.5.37/tests'
make[2]: *** [check-recursive] Error 1
make[2]: Leaving directory `/root/rpmbuild/BUILD/flex-2.5.37/tests'
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory `/root/rpmbuild/BUILD/flex-2.5.37'
make: *** [check] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.TMV40s (%check)


RPM build errors:
    flex-2.5.37-5.el7.src.rpm: Header V3 RSA/SHA256 Signature, key ID fd431d51: NOKEY
    user mockbuild does not exist - using root
    group mockbuild does not exist - using root
    user mockbuild does not exist - using root
    group mockbuild does not exist - using root
    user mockbuild does not exist - using root
    group mockbuild does not exist - using root
    user mockbuild does not exist - using root
    group mockbuild does not exist - using root
    user mockbuild does not exist - using root
    group mockbuild does not exist - using root
    Bad exit status from /var/tmp/rpm-tmp.TMV40s (%check)


Expected results:
Successful build

Additional info:
Comment 2 Edjunior Barbosa Machado 2018-07-13 07:07:06 UTC 
Verified as fixed on flex-2.5.37-6.el7.
Comment 4 errata-xmlrpc 2018-10-30 10:13:29 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:3126