[MacPorts] #20199: qt4-mac fails to build when conflicting ports are active

[MacPorts]

#20199: qt4-mac fails to build when conflicting ports are active
-----------------------------------+----------------------------------------
  Reporter:  jwhowse4@…            |       Owner:  michaelld@…           
      Type:  defect                |      Status:  reopened              
  Priority:  Normal                |   Milestone:                        
 Component:  ports                 |     Version:  1.7.1                 
Resolution:                        |    Keywords:                        
      Port:  qt4-mac               |  
-----------------------------------+----------------------------------------

Comment(by michaelld@…):

 Update on this ticket:  There is no "truly optimal" solution for this
 issue without tweaking the `#include`s themselves in the Qt source.
 Without tweaking the source: Putting MacPorts paths first for searching
 will find the correct libraries and headers, but will result in the
 conflicts already found.  Putting them last will resolve the conflicts --
 I've verified that yesterday; took quite a bit of hacking to get all the
 paths last, but it does work -- but no longer uses certain MacPorts-
 provided libraries and headers.

 IMHO the "best" solution given the above is (1) to patch any violating
 `#include`s in the Qt source to decrease the chances of finding that file
 in some external-to-Qt path (e.g., `${prefix}/include`).  I think this
 patching can be performed dynamically in the Portfile instead of using a
 static patch file.  (2) Move MacPorts search paths to the front of the
 list in order for `configure` to find them.

 So that's what I'll be working towards later today unless someone has a
 better suggestion.  First, hopefully, some good sleep now, to be better
 prepared.

-- 
Ticket URL: <http://trac.macports.org/ticket/20199#comment:84>
MacPorts <http://www.macports.org/>
Ports system for Mac OS