curses.h problem

curses.h problem

Post by Reality is a point of vi » Fri, 19 Jul 1996 04:00:00




 | the line it complains about are:
 | #ifdef __linux__
 | extern speed_t ospeed;  --> this is line 39 of the file.
 | #else
 | extern short ospeed;
 | #endif
 |
 |    Please explain what is the problem and a work around to solve it.
 +----

Offhand I don't know what the problem is but I suspect that
-I/usr/include/ncurses would fix it.

--
Gary Johnson                   "There's no union called the AFL-CIA is there?"

                   CAMPAIGN '96: Juck 'em if they can't fake a toke.

 
 
 

curses.h problem

Post by anonym.. » Sun, 21 Jul 1996 04:00:00



> Path: hermes.is.co.za!news.uoregon.edu!hunter.premier.net!news-res.gsl.net!news.gsl.net!news-penn.gsl.net!news.gsl.net!news.NetVision.net.il!news

> Newsgroups: comp.os.linux.development.apps
> Subject: curses.h problem
> Date: Fri, 19 Jul 1996 00:24:09 +0200
> Organization: Pixel Multimedia
> Lines: 23

> NNTP-Posting-Host: wintermute.pixel.co.il
> Mime-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
> X-Mailer: Mozilla 3.0b3 (X11; I; Linux 1.3.98 i486)

> Hello

> In every program I try to include curses.h I get the following error:

> In file included from /usr/include/cureses.h:42,
>             from source.name:1:
> /usr/include/termcap.h:39:parse error before 'ospeed'
> /usr/include/termcap.h:39: warning: data definition has no type or
> storage class

> the line it complains about are:

> #ifdef __linux__
> extern speed_t ospeed;  --> this is line 39 of the file.
> #else
> extern short ospeed;
> #endif

>    Please explain what is the problem and a work around to solve it.

>    Paolo

speed_t is not type defined.
grep speed_t /usr/include/*.h | grep typedef
to find out where

Regards Philip Shearer



 
 
 

1. curses curses curses

Last year I developed a curses based program on my SUN IPC (Sunos 4.1.2).
Sunos 4.1.2 has a SysV version of curses, that is the version I used.
I recently tried to compile my program with the new SUN C compiler
(version 2.0.1 I think).  The curses routines that come with this compiler
are BSD routines.  BSD curses and SysV curses do not seem to be compatible.
The compilation crashed (unrecognized symbols being a glaring problem).
I logged into a Solaris 2.1 based SUN that also had the new Sun C compiler
installed, and it too had BSD curses.

I would like to know why Sun chose BSD curses for their C compiler.  I
thought they would surely use SysV curses for Solaris 2.x, since it is
SysV based (or does SVR4 use BSD curses by default?).

Is the source for SysV curses available via anon ftp?

Thanks for any help you can send.

--

2. Motif default font size

3. system()'ing a curses app from a curses app

4. cgi and apache

5. Curses?. . .Curses!

6. Searching src files...

7. Mini-curses (or many curses?)

8. Secure File Transfers

9. cursed curses

10. Is _UNIX Curses Explained_ THE book on curses?

11. Curses (Cursed or a blessing?)

12. Curses source/alternatives to curses ?

13. Slow curses - is there a better/faster curses?