>>>>> "e" == ewiz <[EMAIL PROTECTED]> writes:
e> I am trying to compile Xvnc (vnc-3.3.3r1) patched from TightVNC
e> 1.1 gives me a errors when
e> [root@mybox Xvnc]#make World .... ... /bin/sh:
e> ../../../../config/makedepend/makedepend: No such file or
e> directory make[4]: *** [depend] Error 127 ... make[1]: Leaving
e> directory `/home/nagendra/vnc_unixsrc/Xvnc' make: *** [World]
e> Error 2
e> but I have makddepend in my path as below
e> [root@mybox Xvnc]# whereis makedepend makedepend:
e> /usr/X11R6/bin/makedepend /usr/bin/X11/makedepend
e> can anybody let me know what's wrong or how to solve this...I
e> am using XFree86 4.01 on a Mandrake 7.2 installtion.
Xvnc builds its own copy of makedepend from source and in your case it
has failed to build it for some reason. Actual error message is not
shown in part of output you have provided and I guess it's something
like this:
=== cut ===
gcc -O -ansi -pedantic -I../../config/imake -I../../include
-I../../exports/include/X11 -I../.. -I../../exports/include -Dlinux
LinuxMachineDefines -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE
-D_XOPEN_SOURCE=500L -D_BSD_SOURCE -D_SVID_SOURCE -D_REENTRANT
-DFUNCPROTO=15 -DNARROWPROTO -c include.c -o include.o
gcc: cannot specify -o with -c or -S and multiple compilations
make[5]: *** [include.o] Error 1
make[5]: Leaving directory
`/home/user/VNC/vnc_unixsrc/Xvnc/config/makedepend'
=== cut ===
If my guess is correct, this is a problem already reported by other
people but unfortunately I do not have a solution at this moment. The
problem depends on gcc version installed in the system and I think
it's caused by some incompatibilities in command-line syntax between
gcc versions. The reason why I'm not able to solve this problem
immediately is that I have no Linux installations with gcc version
which will behave like yours. But I plan to prepare RPMS for 1.2
release of TightVNC, so it's possible I will be faced with this
problem and I will have to solve it.
If somebody knows the solution already please reply to the mailing
list. As far as I understand, this problem is not specific to VNC
patched for tight encoding; standard VNC should have the same problems
in similar build environments.
e> any help is apperciated...
e> tia ewiz
--
With Best Wishes,
Constantin
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
