Arch Linux User Repository

The second one is a violation of the multiple definition rule. Hard to fix if xmkmf/imake cannot even produce working generated makefiles anymore (one could of course patch the generated makefiles). Adding -Wl,--allow-multiple-definition might not be the smartest of all ideas, but at least Xvnc builds. But I doubt it works.

tightvnc seems to be abandonware..

The imake tools add ar clq as AR to all makefiles, detailed explanation see here: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=56fe2a2033eb3683c487a14e60f3eb130bc7c61f

This solves part one of the compilation issues..

Does not build on Arch:

$ pamac build tightvnc
Preparing...
Cloning tightvnc build files...
Generating tightvnc information...
Checking tightvnc dependencies...
Resolving dependencies...
Checking inter-conflicts...

To build (1):
  tightvnc  1.3.10-10    AUR


Edit build files : [e] 
Apply transaction ? [e/y/N] y
...
/usr/include/features.h:194:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
  194 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE"
      |   ^~~~~~~
rm -f libdix.a
ar clq libdix.a atom.o colormap.o cursor.o devices.o dispatch.o dixutils.o events.o     extension.o gc.o globals.o glyphcurs.o grabs.o  main.o property.o resource.o swaprep.o swapreq.o        tables.o window.o initatoms.o dixfonts.o privates.o pixmap.o          
ar: libdeps specified more than once
make[3]: *** [Makefile:638: libdix.a] Error 1
make[3]: Leaving directory '/var/tmp/pamac-build-user/tightvnc/src/vnc_unixsrc/Xvnc/programs/Xserver/dix'
make[2]: *** [Makefile:783: dix] Error 2
make[2]: Leaving directory '/var/tmp/pamac-build-user/tightvnc/src/vnc_unixsrc/Xvnc/programs/Xserver'
make[1]: *** [Makefile:609: all] Error 2
make[1]: Leaving directory '/var/tmp/pamac-build-user/tightvnc/src/vnc_unixsrc/Xvnc/programs'
make: *** [Makefile:592: all] Error 2
==> ERROR: A failure occurred in build().
    Aborting...

For me building fails with:

/usr/bin/ld: cfb16/libcfb.a(cfballpriv.o):(.bss+0x8): multiple definition of `cfbWindowPrivateIndex'; cfb/libcfb.a(cfballpriv.o):(.bss+0x4): first defined here
/usr/bin/ld: cfb16/libcfb.a(cfballpriv.o):(.bss+0x4): multiple definition of `cfbGCPrivateIndex'; cfb/libcfb.a(cfballpriv.o):(.bss+0x0): first defined here
/usr/bin/ld: cfb16/libcfb.a(cfbbitblt.o):(.bss+0x0): multiple definition of `cfbPuntCopyPlane'; cfb/libcfb.a(cfbbitblt.o):(.bss+0x0): first defined here
/usr/bin/ld: cfb32/libcfb.a(cfballpriv.o):(.bss+0x8): multiple definition of `cfbWindowPrivateIndex'; cfb/libcfb.a(cfballpriv.o):(.bss+0x4): first defined here
/usr/bin/ld: cfb32/libcfb.a(cfballpriv.o):(.bss+0x4): multiple definition of `cfbGCPrivateIndex'; cfb/libcfb.a(cfballpriv.o):(.bss+0x0): first defined here
/usr/bin/ld: cfb32/libcfb.a(cfbbitblt.o):(.bss+0x0): multiple definition of `cfbPuntCopyPlane'; cfb/libcfb.a(cfbbitblt.o):(.bss+0x0): first defined here

Remmina + remmina-plugin-exec (aur) + TigerVNC seems to be a nice way. Remmina is worth it as a GUI and TigerVNC enable VNC connection fast and well set. Use also vncpassword to create a password file. vncpassword ~/.vnc/passwdFileName Then you create an external command in Remmina : vncviewer -PasswordFile /home/username/.vnc/passwdFileName xx.xx.xx.xx:xxxx You have to specify full path

So bad :/ I'm running with TigerVNC but honestly that really meh. I can't find a trusted and working VNC client under Linux. So sad :/

TightVNC seems to have abandonned Linux. The 2.x version is "Windows only". The last Linux version is 1.3.10… :(