1. Attn Rob: Eu 2.5/Error compiling with Watcom
- Posted by Phil Russell <pg_russell at lineone.net> Nov 26, 2004
- 643 views
Rob, I tried compiling winwire.exw using ewc and Open Watcom 1.1. On running emake.bat I get the following: compiling with WATCOM main_.c main_.c(68): Error! E1011: Symbol 'CLK_TCK' has not been declared init_.c winwire.c winwir_0.c dll.c machine.c linking Error! E2008: cannot open main_.obj : No such file or directory I'm not much good with C - am I doing something wrong here? Regards, Phil
2. Re: Attn Rob: Eu 2.5/Error compiling with Watcom
- Posted by Andy Serpa <ac at onehorseshy.com> Nov 26, 2004
- 607 views
Phil Russell wrote: > > Rob, > > I tried compiling winwire.exw using ewc and Open Watcom 1.1. > > On running emake.bat I get the following: > > compiling with WATCOM > main_.c > main_.c(68): Error! E1011: Symbol 'CLK_TCK' has not been declared > init_.c > winwire.c > winwir_0.c > dll.c > machine.c > linking > Error! E2008: cannot open main_.obj : No such file or directory > > I'm not much good with C - am I doing something wrong here? > Works fine for me -- you should probably download the latest Watcom. They are up to 1.3...
3. Re: Attn Rob: Eu 2.5/Error compiling with Watcom
- Posted by Phil Russell <pg_russell at lineone.net> Nov 26, 2004
- 608 views
Andy Serpa wrote: > > Phil Russell wrote: > > > > Rob, > > > > I tried compiling winwire.exw using ewc and Open Watcom 1.1. > > > > On running emake.bat I get the following: > > > > compiling with WATCOM > > main_.c > > main_.c(68): Error! E1011: Symbol 'CLK_TCK' has not been declared > > init_.c > > winwire.c > > winwir_0.c > > dll.c > > machine.c > > linking > > Error! E2008: cannot open main_.obj : No such file or directory > > > > I'm not much good with C - am I doing something wrong here? > > > > Works fine for me -- you should probably download the latest Watcom. They are > up to > 1.3... > Andy, I downloaded Open Watcom 1.3 and reinstalled eu 2.5 but same error Looks like a problem in the generated c-source rather than a compiler error? Thanks anyway. Phil
4. Re: Attn Rob: Eu 2.5/Error compiling with Watcom
- Posted by Robert Craig <rds at RapidEuphoria.com> Nov 26, 2004
- 685 views
Phil Russell wrote: > I tried compiling winwire.exw using ewc and Open Watcom 1.1. > > On running emake.bat I get the following: > > compiling with WATCOM > main_.c > main_.c(68): Error! E1011: Symbol 'CLK_TCK' has not been declared > init_.c > winwire.c > winwir_0.c > dll.c > machine.c > linking > Error! E2008: cannot open main_.obj : No such file or directory > > I'm not much good with C - am I doing something wrong here? CLK_TCK is defined in a WATCOM file called time.h Apparently WATCOM found a version of that file, somewhere, but it doesn't have CLK_TCK. Not all C compilers are standardized on CLK_TCK. Maybe you got time.h from some other compiler installation. WATCOM uses the environment variable INCLUDE to know where to look for include files. On my machine, if I type SET, I see (among many other variables) INCLUDE=C:\WATCOM\H;C:\WATCOM\H\NT I wonder if you just need to reboot to set this variable. I don't have Open Watcom. I still use 10.6, but others who use Open Watcom have not had any trouble. Regards, Rob Craig Rapid Deployment Software http://www.RapidEuphoria.com
5. Re: Attn Rob: Eu 2.5/Error compiling with Watcom
- Posted by Phil Russell <pg_russell at lineone.net> Nov 26, 2004
- 610 views
- Last edited Nov 27, 2004
Robert Craig wrote: > > > CLK_TCK is defined in a WATCOM file called time.h > Apparently WATCOM found a version of that file, > somewhere, but it doesn't have CLK_TCK. Not all C compilers > are standardized on CLK_TCK. > Maybe you got time.h from some other compiler > installation. WATCOM uses the environment > variable INCLUDE to know where to look for include files. > On my machine, if I type SET, I see (among many other variables) > INCLUDE=C:\WATCOM\H;C:\WATCOM\H\NT > I wonder if you just need to reboot to set this variable. > I don't have Open Watcom. I still use 10.6, but others > who use Open Watcom have not had any trouble. > Yep, that was it. Works fine now. Many thanks, Phil