Source: tightvnc
Version: 1:1.3.9-9
Severity: serious
https://buildd.debian.org/status/package.php?p=tightvnc
...
gcc -o Xvnc -O2 -ansi -pedantic -L../.././/exports/lib dix/libdix.a
os/libos.a ../.././/lib/Xau/libXau.a ../.././/lib/Xdmcp/libXdmcp.a
../.././/exports/lib/libfont.a hw/vnc/libvnc.a
../.././/../libvncauth/libvncauth.a cfb/libcfb.a cfb16/libcfb.a cfb24/libcfb.a
cfb32/libcfb.a mfb/libmfb.a dix/libxpstubs.a mi/libmi.a Xext/libext.a
-lz -lm -rdynamic -ldl -L/usr/local/lib -ljpeg -lz
-lcrypt -Wl,-rpath-link,../.././/exports/lib
/usr/bin/ld: cfb/libcfb.a(stipmips.o): relocation R_MIPS_HI16 against `a local
symbol' can not be used when making a shared object; recompile with -fPIC
cfb/libcfb.a: error adding symbols: Bad value
collect2: error: ld returned 1 exit status
Makefile:718: recipe for target 'Xvnc' failed
make[4]: *** [Xvnc] Error 1
The error message is misleading, the problem is actually
PIE versus stipmips.s
One option would be to disable PIE when building tightvnc.
But stipmips.s is assembler code Keith wronte in 1990 (sic).
I doubt this is still required today and would suggest to
fix this FTBFS by nuking the HAS_STIPPLE_CODE parts from
Xvnc/programs/Xserver/cfb/Imakefile so that the C code is
used like on all other release architectures.
