Bug 1323065

Summary: tigervnc cannot build against xorg-x11-server-source
Product: Red Hat Enterprise Linux 6 Reporter: Tomas Pelka <tpelka>
Component: tigervncAssignee: Jan Grulich <jgrulich>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.8CC: jkoten, tpelka
Target Milestone: rcKeywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1063392 Environment:
Last Closed: 2017-03-21 09:52:51 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:
Bug Depends On:    
Bug Blocks: 1269194    

Description Tomas Pelka 2016-04-01 07:36:33 UTC
+++ This bug was initially created as a clone of Bug #1063392 +++

Description of problem:
When building tigervnc in rawhide I get this:

Xvnc-miinitext.o:(.data.rel+0x1c8): undefined reference to `dri3_extension_init'
collect2: error: ld returned 1 exit status

Version-Release number of selected component (if applicable):
xorg-x11-server-source-1.15.0-3.fc21

Works fine when building in f20 against xorg-x11-server-source-1.14.4-6.fc20.

--- Additional comment from Tim Waugh on 2014-03-17 12:58:04 EDT ---

I'm still seeing this.

--- Additional comment from Tim Waugh on 2014-03-19 07:58:48 EDT ---

Not sure why this would block bug #1051573 specifically. I'm seeing this failure on x86_64.

--- Additional comment from Tim Waugh on 2014-03-19 13:27:28 EDT ---

Fixed by disabling dri3 in the configure line.

--- Additional comment from Yaakov Selkowitz on 2014-04-06 14:01:57 EDT ---

The attached patch for rawhide should allow the build to succeed with DRI3 and Present enabled.

--- Additional comment from Tim Waugh on 2014-04-07 06:45:30 EDT ---

Thanks! Built in tigervnc-1.3.1-2.fc21.

Comment 9 errata-xmlrpc 2017-03-21 09:52:51 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/RHSA-2017-0630.html