TightVNC, Slack10, Compiling Errors

sovietpower · 01-30-2005, 01:13 AM

I have a slack10 box that had TightVNC installed but I had to reinstall Slack 10. It was setup to be accessible by VNC and SSH. I have restored my SSH capability but TightVNC refuses to compile correctly from source. I know thats how I did it last time as there are no slack packages for it. It I do what is required as followed

xmkmf

that works

next

make World

this is where I get the errors

gcc: cannot specify -o with -c or -S and multiple compilations
make[2]: *** [vncauth.o] Error 1
make[2]: Leaving directory `/home/baked/vnc_unixsrc/libvncauth'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/baked/vnc_unixsrc'
make: *** [World] Error 2

I had it working before can anyone help me with this???

kdegraaf · 02-16-2005, 09:02 AM

This is a bug with imake (xmkmf). The symbol DefaultGcc2i386Opt is supposed to be translated to a series of options before compilation. If xmkmf ignores it and it's not translated, gcc thinks it's being asked to compile two files at once, hence the error.

One workaround is to add the following to /usr/X11R6/lib/X11/config/linux.cf:

Code:

#ifndef DefaultGcc2i386Opt
#  define DefaultGcc2i386Opt -O3
#endif