[MacPorts] #46282: Tightvnc not building

[MacPorts]

#46282: Tightvnc not building
------------------------+--------------------------------
  Reporter:  jschewe@…  |      Owner:  macports-tickets@…
      Type:  defect     |     Status:  new
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:  2.3.3
Resolution:             |   Keywords:
      Port:  tightvnc   |
------------------------+--------------------------------
Changes (by ryandesign@…):

 * cc: ryandesign@… (added)


Comment:

 imake is an ancient build system which uses the C preprocessor for unusual
 purposes. It requires the "traditional" mode of the C preprocessor,
 specifically GCC's C preprocessor. As of Xcode 5, only the clang compiler
 is provided; its C preprocessing mode does not function the same way as
 GCC's "traditional" C preprocessor, to the extent that it breaks imake.

 We fixed the imake port by forcing it to use the "traditional" C
 preprocessor installed by the tradcpp port instead of the C preprocessor
 provided by Xcode's compilers. However tightvnc's build is convoluted,
 involving many separate directories. One of those directories, Xvnc, is
 not included in the main part of the build, so we have to do that part
 later, in a post-build block. This is the part that's failing. I believe
 it's failing because that part of the build includes its own private copy
 of imake, one which has not been fixed for this problem.

 I would like to see if we can make that part of the build use the already-
 installed and already-fixed copy of imake. If not, we can bring the fixes
 from the imake port into the tightvnc port's private copy of imake.

-- 
Ticket URL: <https://trac.macports.org/ticket/46282#comment:2>
MacPorts <https://www.macports.org/>
Ports system for OS X