Bug 107918 - unixODBC src rpm missing XFree86-devel from dependancy listing
Summary: unixODBC src rpm missing XFree86-devel from dependancy listing
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: unixODBC
Version: 3.0
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
Assignee: Fernando Nasser
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-10-24 13:26 UTC by Clifford Perry
Modified: 2007-11-30 22:06 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-10-24 14:13:41 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Clifford Perry 2003-10-24 13:26:11 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030708

Description of problem:
While attempting to recompile unixODBC on a RH ES 3 system it errored with the
following message :

checking for gethostbyname in -lnsl... yes
checking for X... configure: error: Can't find X includes. Please check your
installation and add the correct paths!
error: Bad exit status from /var/tmp/rpm-tmp.82172 (%build)


RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.82172 (%build)
[root@rhes3-build root]# 

To resolve this, I used the up2date command to download and install the
XFree86-devel-4.3.0-35.EL rpm and then tryed to compile again, this time
sucessfully. I would suggest that adding XFree86-devel to the BuildPrereq within
the unixODBC.spec file would be an ideal solution:

BuildPrereq: kdelibs-devel qt-devel libmng-devel XFree86-devel

Clifford. 

Version-Release number of selected component (if applicable):
unixODBC-2.2.3-6

How reproducible:
Always

Steps to Reproduce:
1. Get ES 3 system without XFree86-devel installed
2. download and install the unixODBC src rpm for RH ES 3
3. attempt to recompile from source. 
    

Additional info:
Comment 1 Fernando Nasser 2003-10-24 14:13:41 UTC 
Suggestion accepted. Thanks.  It will be in the next release.
Note You need to log in before you can comment on or make changes to this bug.