Bug 1189893

Summary:	Rebuilding openmotif from source on 6.6
Product:	Red Hat Enterprise Linux 6	Reporter:	DHC <deadhorseconsulting>
Component:	openmotif	Assignee:	Thomas Woerner <twoerner>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.6	CC:	carandraug+dev, tpelka
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-21 11:24:50 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:

Description DHC 2015-02-05 18:30:03 UTC

Description of problem:
This has been previously submitted and labeled not-a-bug, but it really is a bug in the .spec file.  

The package won't build unless flex and now with version 6.6 flex-devel are installed.  The relevant flex library actually contains a main() function -- and when linked against the library, the software builds correctly.  

I recommend adding a BuildRequires for flex-devel in the .spec files for both openmotif and openmotif22.

Version-Release number of selected component (if applicable):
openmotif-2.3.3-8.el6
openmotif-2.3.3-8.el6

How reproducible:
Always


Steps to Reproduce:
1. Install a development system with RedHat 6.6
2. Ensure that flex and flex-devel are not installed
3. Try building the package with rpmbuild.  The build will fail.
4. Install flex-devel.
5. Retry the package build.  The build will work.

Comment 2 Carnë Draug 2015-03-11 11:40:34 UTC

I can confirm this bug.

Installing flex-devel fixed the issue and it build fine afterwards. The spec file is missing a BuildRequires

Comment 9 errata-xmlrpc 2017-03-21 11:24:50 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://rhn.redhat.com/errata/RHBA-2017-0743.html