#40862: tightvnc @1.3.10: fatal error: ' X11 .rules' file not found --------------------------+-------------------------------- Reporter: dylanryan@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: | Keywords: mavericks Port: tightvnc | --------------------------+-------------------------------- Comment (by ryandesign@…): Replying to [comment:16 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. -- Ticket URL: <https://trac.macports.org/ticket/40862#comment:17> MacPorts <http://www.macports.org/> Ports system for OS X