Applied the patch succesfully against 4.1 net/tightvnc, but getting the following error:

# make install

(...)

gcc -c -O2 -Dasm=__asm -I. -I../include -I../../../include/fonts -I../../.././/exports/include/X11 -I../../.././/include/fonts -I../../.././ -I../../.././/exports/include -DCSRG_BASED -DSHAPE -DGCCUSESGAS -DNDEBUG -DFUNCPROTO=15 -DNARROWPROTO mibitblt.c
mibitblt.c: In function `miGetPlane':
mibitblt.c:300: error: `CARD64' undeclared (first use in this function)
mibitblt.c:300: error: (Each undeclared identifier is reported only once
mibitblt.c:300: error: for each function it appears in.)
mibitblt.c:300: error: `pOut' undeclared (first use in this function)
mibitblt.c:312: error: syntax error before ')' token
mibitblt.c:355: error: syntax error before "bit"
*** Error code 1

Stop in /usr/ports/net/tightvnc/w-tightvnc-1.3.8_unixsrc/vnc_unixsrc/Xvnc/programs/Xserver/mi.
*** Error code 1

Stop in /usr/ports/net/tightvnc/w-tightvnc-1.3.8_unixsrc/vnc_unixsrc/Xvnc/programs/Xserver (line 659 of Makefile).
*** Error code 1

Stop in /usr/ports/net/tightvnc/w-tightvnc-1.3.8_unixsrc/vnc_unixsrc/Xvnc/programs (line 562 of Makefile).
*** Error code 1

Stop in /usr/ports/net/tightvnc/w-tightvnc-1.3.8_unixsrc/vnc_unixsrc/Xvnc (line 546 of Makefile).
*** Error code 1

Stop in /usr/ports/net/tightvnc/w-tightvnc-1.3.8_unixsrc/vnc_unixsrc (line 1034 of Makefile).
*** Error code 1

Stop in /usr/ports/net/tightvnc (line 2063 of /usr/ports/infrastructure/mk/bsd.port.mk).
*** Error code 1

Stop in /usr/ports/net/tightvnc (line 1373 of /usr/ports/infrastructure/mk/bsd.port.mk).
*** Error code 1

Stop in /usr/ports/net/tightvnc (line 1861 of /usr/ports/infrastructure/mk/bsd.port.mk).
*** Error code 1

Stop in /usr/ports/net/tightvnc (line 1400 of /usr/ports/infrastructure/mk/bsd.port.mk).
#

On Tue, 8 May 2007, Stuart Henderson wrote:

On 2007/05/08 13:13, [EMAIL PROTECTED] wrote:
I did the for 4.0 update that Stuart is referring to.

Yes, I updated it to apply to what was -current at the time;
it worked in February and still applies cleanly to an OPENBSD_4_1
ports checkout, I wouldn't expect any problems on 4.1

http://spacehopper.org/openbsd/tightvnc-1.3.8-update.txt

Reply via email to