home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!agate!doc.ic.ac.uk!uknet!gdt!uwe-bristol!r_voisey
- From: r_voisey@csd.uwe.ac.uk (R Voisey)
- Newsgroups: comp.sys.acorn.tech
- Subject: Re: Curses, foiled again.
- Message-ID: <1993Jan28.104851.14447@csd.uwe.ac.uk>
- Date: 28 Jan 93 10:48:51 GMT
- References: <727749140snx@klaatu.demon.co.uk>
- Organization: University of the West of England, Bristol
- Lines: 33
-
- In article <727749140snx@klaatu.demon.co.uk> steve@klaatu.demon.co.uk writes:
- >the compiler and see what happens. It complains that it can't find
- >"sgtty.h", and sure enough I don't seem to have anything called that
-
- sgtty.h is an include file which usually just includes (into itself) the
- system dependent headers concerned with talking to terminals. I vaguely
- recall that in unix ioctl.h is included, which contains mainly compiler
- definitions (such as BELL 07 etc). It also contains some very OS
- dependent stuff such as socket support etc.
-
- So, basically, it's specific to Unix (and a couple of similar OSs) so does
- not appear in the standard Archimedes C library. You'll have to remove
- the #include <sgtty.h> statement, then run it through the compiler again
- and see what it complains about. I haven't seen the source in question, but
- it's possible it just uses a few of the compiler definitions which you can
- pick out of the throwback and derive yourself. If, however, it expects to
- use sockets, pipes and so forth you have a problem.
-
- >Any suggestions as to what I can do now? ("Give
- >up, you fool" is acceptable, and very tempting, although things did seem
- >to be going rather well up until this point).
-
- I recall that somebody did a Unix library for the Arch, so maybe it will
- make life easier (I haven't seen it). If not, you're in for some fun I
- suspect.
-
- Cheers
-
- Bob
- --
- Robert J. Voisey : r_voisey@csd.uwe.ac.uk
- -- Probug Software Developments --
- 162 Staplehill Rd, Fishponds, Bristol, Avon, England
-