randy@rls.UUCP (Randall L. Smith) (08/09/89)
Does anyone have a PD text.h and gdisk.h for the monitor sources? In building monitor for Microport 386, System V, make says, ./include/km/monitor.h: 19: Can't find include file sys/text.h ./include/km/monitor.h: 28: Can't find include file sys/gdisk.h This seem to be Xenix dependant code. What are they? What gives? Are there known ways to code around these dependancies? Have I asked enough questions? :-) Any help will be greatly appreciated. Cheers! - randy Usenet: randy@rls.uucp Bangpath: ...<backbone>!osu-cis!rls!randy Internet: rls!randy@tut.cis.ohio-state.edu
guy@auspex.auspex.com (Guy Harris) (08/10/89)
>Does anyone have a PD text.h and gdisk.h for the monitor sources? In >building monitor for Microport 386, System V, make says, > >./include/km/monitor.h: 19: Can't find include file sys/text.h >./include/km/monitor.h: 28: Can't find include file sys/gdisk.h > >This seem to be Xenix dependant code. What are they? What gives? Are >there known ways to code around these dependancies? Have I asked enough >questions? :-) Any help will be greatly appreciated. Time to point this out again: If you're trying to compile a program originally written for flavor X of UNIX, and it won't compile on your flavor Y system because some include files are missing, it's quite often the case that the absence of the include files is a symptom of a deeper problem with getting that program to run on flavor Y. The include files may be missing because the mechanism for which they define data structures, etc. may be missing. In the case of <sys/text.h>, this appears to be the case - System V Release 3 doesn't have "traditional" UNIX text segments (which I assume the version of Xenix on which "monitor" worked still had), it has "regions" instead. This means that if "monitor" depends on having a "struct text" in your system, the parts that depend on it will have to be rewritten to handle the region data structures instead.