Tightvnc not building

[jschewe@…]

I can't build tightvnc anymore. The problem in ticket:32864 appears to have come up again. Also may be related to ticket:31504. Maybe related to #41408.

I'm running on Mavericks with the latest OS and Xcode updates.

>uname -a
Darwin butterfield.bbn.com 13.4.0 Darwin Kernel Version 13.4.0: Sun Aug 17 19:50:11 PDT 2014; root:xnu-2422.115.4~1/RELEASE_X86_64 x86_64

>cc --version
Apple LLVM version 6.0 (clang-600.0.56) (based on LLVM 3.5svn)
Target: x86_64-apple-darwin13.4.0
Thread model: posix

Build log is attached.

[ryandesign (Ryan Carsten Schmidt)]

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.

[mf2k (Frank Schima)]

Duplicate of #40862