tightvnc @1.3.10: fatal error: ' X11 .rules' file not found

[dylanryan]

Rebuilding port tree after installing mavericks.

tightvnc is failing to build very early on. Build log included. Relevant part appears to be:

--->  Configuring tightvnc
mv -f Makefile Makefile.bak
imake -DUseInstalled -I/opt/local/lib/X11/config
In file included from Imakefile.c:15:
/opt/local/lib/X11/config/Imake.tmpl:2144:10: fatal error: ' X11 .rules' file not found
#include ProjectRulesFile
         ^
/opt/local/lib/X11/config/Imake.tmpl:2142:35: note: expanded from macro 'ProjectRulesFile'
# define ProjectRulesFile       Concat3(<,TopLevelProject,.rules>)
                                        ^
/opt/local/lib/X11/config/Imake.rules:256:23: note: expanded from macro 'Concat3'
#define Concat3(a,b,c)a/**/b/**/c
                      ^
1 error generated.
imake: Exit code 1.
  Stop.

[sck-nogas (Scott C. Kennedy)]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #41222.

[brian.wix@…]

Cc Me!

[cooljeanius (Eric Gallager)]

Cc Me!

[stannous@…]

Cc Me!

[chihangli@…]

Cc Me!

[mf2k (Frank Schima)]

Cc Me!

[chihangli@…]

Cc Me!

[nathanielbailey@…]

OSX Mavericks no longer supports X11 -- you need Xquartz

Apple Documentation ​http://support.apple.com/kb/ht5293

Main Website: ​http://xquartz.macosforge.org/landing/

[dylanryan]

I've had xquartz installed (and kept up to date) for a long time (... Lion? Earlier?). No help for me. Tried reinstalling it for kicks. No luck.

I suspect the problem is that it is looking for " X11 .rules" (note the leading space, and space before the period!). tightvnc comes with a "X11.rules" (no spaces), but it is looking for it with a space. Based on the macro noted in my OP, my guess is that it is expecting the comments in Concat3 to be replaced with the empty string, but instead they are being replaced with whitespace.

[nathanielbailey@…]

Yeah.. I'm getting a different issue all together when I upgrade so I will be opening another ticket. Sorry I couldn't help.

[ryandesign (Ryan Carsten Schmidt)]

Replying to nathanielbailey@…:

OSX Mavericks no longer supports X11 -- you need Xquartz

That has nothing to do with this ticket.

Replying to dylanryan@…:

I suspect the problem is that it is looking for " X11 .rules" (note the leading space, and space before the period!). tightvnc comes with a "X11.rules" (no spaces), but it is looking for it with a space. Based on the macro noted in my OP, my guess is that it is expecting the comments in Concat3 to be replaced with the empty string, but instead they are being replaced with whitespace.

Yes, the problem is that clang's cpp (which is the only cpp available as of Xcode 5) does not handle this antique build system the way gcc's cpp did. We need to either fix the build system (in all the (thankfully few) ports still using imake) to work with clang's cpp or instruct them not to use clang's cpp.

Replying to nathanielbailey@…:

Yeah.. I'm getting a different issue all together when I upgrade so I will be opening another ticket. Sorry I couldn't help.

Your ticket #41830 shows exactly the same error as this ticket.

[nathanielbailey@…]

Well -- thanks for getting back to us. I thought X11 and compiler issues were two different issues so I was just being due diligent and trying to post what I had. Now "looking" at his updated log file (which I forgot to do) -- your right it does show the same 'xmkmf' error I was getting.

I assume updating to clang would be easier considering that's what apple is moving forward to and you don't want to start using deprecated stuff hehe.

-=-=-

I use this for work and "thankfully" tighvnc still works for me, it just won't update. I hope this gets updated asap so I can keep everything up to date and working.

This is the only port I have installed that won't update, and of course its the one I use like 50 times a day.

[stannous@…]

Not a real workaround for tightvnc lovers, but will keep you going without resorting to "chicken": just install vnc. I tried tigervnc but my mouse didn't seem to work. Tried real vnc (port install vnc) and that worked fine. Didn't have to change any of my config.

[nathanielbailey@…]

The "main" reason I need tightvnc is because of the '-via' option. This creates SSH tunneling and vncviewer via tighvnc can be run via command line script and not from an SSH window. I work on multiple servers a day and having a script and using the -via option is pretty much the only way to go without running a linux box in order to run tightvnc.

I found this project: ​http://www.karlrunge.com/x11vnc/ssvnc.html

But I'm not sure if this works. I don't want to ruin my current install of tighvnc to try something that may not work and not be able to get work done.

Any suggestions?

[ryandesign (Ryan Carsten Schmidt)]

Replying to nathanielbailey@…:

The "main" reason I need tightvnc is because of the '-via' option. This creates SSH tunneling and vncviewer via tighvnc can be run via command line script and not from an SSH window. I work on multiple servers a day and having a script and using the -via option is pretty much the only way to go without running a linux box in order to run tightvnc.

I found this project: ​http://www.karlrunge.com/x11vnc/ssvnc.html

But I'm not sure if this works.

Well you could try it out. I was not familiar with ssvnc but from what I can tell it is a patched version of tightvnc and wrapper scripts distributed as a precompiled binary that you can put on a USB stick or other convenient location. As such, it should not affect anything you do with MacPorts.

They also provide a source distribution from which we could attempt to make a port in MacPorts. However according to the readme it still uses imake so it would also suffer from the problem reported in this ticket.

I don't want to ruin my current install of tighvnc to try something that may not work and not be able to get work done.

As long as you don't run "sudo port uninstall tightvnc", your old tightvnc installation should continue to exist.

Any suggestions?

We need to either fix this port and other imake-using ports to work with clang's cpp, or make them depend on and use e.g. gcc-4.8's cpp instead.

[yangtj207@…]

Cc Me!

[diekhans (Mark Diekhans)]

Cc Me!

[WolfgangFahl (Wolfgang Fahl)]

To work around the issue I asked the following question on stackoverflow: ​http://stackoverflow.com/questions/22071308/how-to-fix-the-concat3-macro-in-imake-rules-to-get-tightvnc-compiled

[cooljeanius (Eric Gallager)]

#42547 has a proposed fix for using imake with clang, not sure if that fixes this, as well (but I guess that it should)...

[mf2k (Frank Schima)]

Has duplicate #43908.

[MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)]

Cc Me!

[larryv (Lawrence Velázquez)]

Has duplicate #45487.

[mf2k (Frank Schima)]

Has duplicate #46282.

[ryandesign (Ryan Carsten Schmidt)]

Although we fixed the problem with the imake port, tightvnc is special in that it includes its own private copy of imake which has not been fixed yet. Duplicate #46282 has more information.

[Dmole (Tim)]

Cc Me!

[Dmole (Tim)]

Error: org.macports.build for port tightvnc returned: command execution failed
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port tightvnc failed

but no error in the log...

[mf2k (Frank Schima)]

Cc reporter of duplicate #46726.

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #48248.

[hgonzale (Humberto Gonzalez)]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

Has duplicates #50714, #50715.

[MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)]

I was able to get past the cpp problems with the attached patch files, but tightvnc still fails to compile.
Others seem to have run into ​similar problems.

[myb121@…]

Replying to mcalhoun@…:

I was able to get past the cpp problems with the attached patch files, but tightvnc still fails to compile.
Others seem to have run into ​similar problems.

Were you able to fix the problem with the patch? If so could you explain how to apply patch?

[myb121@…]

Cc Me!

[jmroot (Joshua Root)]

In f9df3a3f464d3dba464252864359784b67bcb06e/macports-ports (master):

tightvnc: build fixes

Thanks to mcalhoun for the first part of the patch.
Fixes: #40862