I can't seem to get Xvnc to compile.  I looked for things to change in
./config/cf, but there are a ton of files in there and I have no idea
what any of them do.  I was scared that if I started editing them I
would just make things worse.  The following is what happens when I type
'make World' in the Xvnc directory:

Building Release 6.3 of the X Window System.

I hope you checked the configuration parameters in ./config/cf
to see if you need to pass BOOTSTRAPCFLAGS.

Wed Feb  7 00:30:21 EST 2001

cd ./config/imake && make  -f Makefile.ini BOOTSTRAPCFLAGS="" clean
make[1]: Entering directory
`/home/ferret/tarball/vnc_unixsrc/Xvnc/config/imake'
rm -f ccimake imake.o imake
rm -f *.CKP *.ln *.BAK *.bak *.o core errs ,* *~ *.a tags TAGS make.log
\#*
rm -f -r Makefile.proto Makefile Makefile.dep bootstrap
make[1]: Leaving directory
`/home/ferret/tarball/vnc_unixsrc/Xvnc/config/imake'
make  Makefile.boot
make[1]: Entering directory `/home/ferret/tarball/vnc_unixsrc/Xvnc'
cd ./config/imake && make -w -f Makefile.ini BOOTSTRAPCFLAGS=""
make[2]: Entering directory
`/home/ferret/tarball/vnc_unixsrc/Xvnc/config/imake'
making imake with BOOTSTRAPCFLAGS= in config/imake
cc -o ccimake  -O -I../../include -I../../imports/x11/include/X11
ccimake.c
cc -c  -O -I../../include -I../../imports/x11/include/X11 `./ccimake`
imake.c
cc -o imake  -O -I../../include -I../../imports/x11/include/X11 imake.o
make[2]: Leaving directory
`/home/ferret/tarball/vnc_unixsrc/Xvnc/config/imake'
rm -f ./config/makedepend/Makefile.proto
./config/imake/imake -I./config/cf  -s
./config/makedepend/Makefile.proto -f ./config/makedepend/Imakefile
-DTOPDIR=../.. -DCURDIR=./config/makedepend
cd ./config/makedepend && rm -f -r Makefile Makefile.dep makedepend *.o
bootstrap
cd ./config/makedepend && make -f Makefile.proto bootstrap
make[2]: Entering directory
`/home/ferret/tarball/vnc_unixsrc/Xvnc/config/makedepend'
make[2]: Nothing to be done for `bootstrap'.
make[2]: Leaving directory
`/home/ferret/tarball/vnc_unixsrc/Xvnc/config/makedepend'
./config/imake/imake -I./config/cf  -s ./config/imake/Makefile.proto -f
./config/imake/Imakefile -DTOPDIR=../.. -DCURDIR=./config/imake
cd ./config/imake && make -f Makefile.proto bootstrapdepend
make[2]: Entering directory
`/home/ferret/tarball/vnc_unixsrc/Xvnc/config/imake'
make[2]: Nothing to be done for `bootstrapdepend'.
make[2]: Leaving directory
`/home/ferret/tarball/vnc_unixsrc/Xvnc/config/imake'
cd ./config/imake && make -w -f Makefile.ini BOOTSTRAPCFLAGS=""
bootstrap
make[2]: Entering directory
`/home/ferret/tarball/vnc_unixsrc/Xvnc/config/imake'
+ mkdir bootstrap
mv *.o imake bootstrap
make[2]: Leaving directory
`/home/ferret/tarball/vnc_unixsrc/Xvnc/config/imake'
cd ./config/imake && make -f Makefile.proto all
make[2]: Entering directory
`/home/ferret/tarball/vnc_unixsrc/Xvnc/config/imake'
gcc -O -ansi -pedantic  -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    -DCPP_PROGRAM="\"/lib/cpp\""   -c -o imake.o imake.c
gcc: cannot specify -o with -c or -S and multiple compilations
make[2]: *** [imake.o] Error 1
make[2]: Leaving directory
`/home/ferret/tarball/vnc_unixsrc/Xvnc/config/imake'
make[1]: *** [imake.bootstrap] Error 2
make[1]: Leaving directory `/home/ferret/tarball/vnc_unixsrc/Xvnc'
make: *** [World] Error 2

The system I'm on is a dual processor SPARCstation 20 running Red Hat
Linux Sparc 6.2.  The reason I'm trying to compile my own is that the
RPM of vnc from RH Sparc PowerTools 6.2 doesn't seem to work.  When I
connect to a vncserver running on the sparc, all the graphics are
garbled, but the viewer works fine to connect to my windows box.  Any
help would be greatly appreciated.

-Steve
---------------------------------------------------------------------
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
---------------------------------------------------------------------

Reply via email to