From: Dave Y. <dav...@gm...> - 2013-12-10 20:53:53
|
On 12/10/13 10:35 am, H. Peter Anvin wrote: > On 12/10/2013 09:41 AM, Dave Yeo wrote: >> On 12/10/13 08:30 am, H. Peter Anvin wrote: >>> Are you building from git or tarball? >> >> I was building from tarball. Testing git head the compile ends with >> f:/usr/bin/sh.exe: ASCIIDOC@: No such file or directory >> make: *** [nasm.xml] Error 1 > > OK, will look at it. Thanks > >> I hadn't tried using OW (1.9) for a while. Compiling from tarball is now >> broken (and git head fails due to Error(F41): No DEFAULT commands for >> making (insns.pl)) >> wcl386 -c -zq -6 -ox -wx -ze -fpi -bt=OS2 -I"I:\WATCOM/h" >> -I"I:\WATCOM/h/os2" -I. -I. -DHAVE_CONFIG_H -fo=parser.obj parser.c >> parser.c(224): Error! E1078: Invalid type for switch expression >> parser.c(1034): Warning! W124: Comparison result always 1 >> parser.c(1036): Warning! W124: Comparison result always 1 >> parser.c(1047): Error! E1078: Invalid type for switch expression >> Error: Compiler returned a bad status compiling "parser.c" >> Error(E42): Last command making (parser.obj;os2) returned a bad status >> Error(E02): Make execution terminated >> > > Yes, I think OpenWatcom is beyond help, sadly. You said you were > building using gcc; is that an environment that can be ported to a Linux > host? I tried at one point cross-compiling a gcc for OS/2 on Linux, but > there were some OS/2-isms in some of the patched files that made it not > work. > I don't know of anyone who has ported the environment to Linux though in theory it should be possible. Dave |