Thanks for replies...
yep you have guessed it correctly I have the excate same problem as you
described........here is more info..
[root@mybox /root]# rpm -q gcc egcs
gcc-2.95.2-12mdk
package egcs is not installed
-----makedepend error--------
gcc: cannot specify -o with -c or -S and multiple compilations
make[4]: *** [include.o] Error 1
-----makedepend error--------
I think the above gcc is not old but is egcs required for the compile
also ? if not what would be the gcc version that it has been sucessfuly
compiled on ? so that I can just install the gcc which works and
compile...
thanks again..
ewiz
Jonathan Morton wrote:
>
> >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.
>
> Can we have the GCC version number, ie the output of 'gcc -v'? Your
> distribution name and version may also be helpful. Also, does your error
> message (roughly) match the one above? I suspect an ancient compiler,
> myself.
>
> For reference, my compiler versions are "egcs-2.91.66" (from RedHat 6.1)
> and "gcc 2.95.2" (built myself on a RedHat 6.2 system), and I don't recall
> having had any problems with them ever.
>
> Note that the technique used in the build command is in wide usage these
> days (building object files from source, then linking the object files in a
> later command, not shown), but the precise syntax may not be.
>
> --------------------------------------------------------------
> from: Jonathan "Chromatix" Morton
> mail: [EMAIL PROTECTED] (not for attachments)
> big-mail: [EMAIL PROTECTED]
> uni-mail: [EMAIL PROTECTED]
>
> The key to knowledge is not to rely on people to teach you it.
>
> Get VNC Server for Macintosh from http://www.chromatix.uklinux.net/vnc/
>
> -----BEGIN GEEK CODE BLOCK-----
> Version 3.12
> GCS$/E/S dpu(!) s:- a20 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$ V? PS
> PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r- y+
> -----END GEEK CODE BLOCK-----
> ---------------------------------------------------------------------
> 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
> ---------------------------------------------------------------------
---------------------------------------------------------------------
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
---------------------------------------------------------------------
