[Prev][Next][Index]

Problems with /usr/include/signal.h in SGIs



A few days ago I sent this message about a problem with the standard
include file <signal.h> on the SGIs. I haven't got any answer yet. Could
someone give me a hand with this? I'm really desperate. Thanks.

Diego.

Forwarded message:
> From diego Mon Jul 17 15:01:12 1995
> Subject: Problems with /usr/include/signal.h in SGIs
> To: sage-bugs@extreme.indiana.edu (Sage Bug Reports)
> Date: Mon, 17 Jul 1995 15:01:12 -0600 (MDT)
> 
> 
> We are trying to unparse a C file that included <signal.h> - The
> original file looks like:
> 
> extern int sigaction(int, const struct sigaction *, struct sigaction *);
>                           ^^^^^^^^^^^^^^^^^^^^^^^^
> 
> But the unparsed source looks like:
> 
> extern int sigaction(int , typedef const   *, struct sigaction *);
>                            ^^^^^^^^^^^^^^^^^
> 
> The system is IRIX 5.3 and GCC v2.6.3
> 
> On a related problem, when the user typedef's a structure that already
> has a name, one of the symbols loses the field information.
> 
> typedef struct abc {
>    ...
> } ABC;
> 
> If the user declares a symbol of type 'struct abc' I cannot access the
> structure fields (abc->symbol()->type() is NULL). To access the fields I
> must force the user to declare symbols with type 'ABC'. Can this be
> fixed?
> 
> 
> Thanks. Diego.


-- 
Diego Novillo (diego@cs.ualberta.ca)    |      Dept of Computing Science
WWW http://web.cs.ualberta.ca/~diego    |          University of Alberta
Use 'finger' to get my PGP public key   |     Edmonton, Alberta - Canada