Compilation on Solaris10 m/c

I am got this error during the compilation on my soalris10 build build
machine, Can anyone help?

I know of the reason the probably it ran out of virtual memory during
the process n so it threw this error. Is there any reason other than
this?

"../ie_ptli.c", line 1199: Warning: String literal converted to char*
in formal argument errDesc in call to SLogError(unsigned char, unsigned
char, unsigned short, char*, long, unsigned long, unsigned long,
unsigned long, char*).
21 Warning(s) detected.
CC: fork failed
"
m waiting :S

.

Relevant Pages

  • Re: Malcolms new book
    ... negative yet you use a signed type which accepts negative values, ... *must* be some special reason for allowing negative length values. ... There are good reasons to use size_t for buffer sizes (mostly ... not prevent passing in a char, it simply requires that the value of the ...
    (comp.lang.c)
  • Re: Malcolms new book
    ... negative yet you use a signed type which accepts negative values, ... *must* be some special reason for allowing negative length values. ... Since a buffer can never have a size less than zero, ... not prevent passing in a char, it simply requires that the value of the ...
    (comp.lang.c)
  • Re: HELP!!
    ... char txtFile; ... getting Segmentation fault here** ... What if malloc() fails and returns a null pointer? ... reasonable implementation, but there's no reason not to avoid malloc ...
    (comp.lang.c)
  • Re: Comments on my code?
    ... value in a char *. ... void *malloc; ... There's simply no good reason not to ... You can still write working archaic code if ...
    (comp.lang.c)
  • Re: C89, size_t, and long
    ... The evidence you present suggests that they are incompetent. ... Suggesting that they are avoiding the standard headers because they think some implementation has headers broken enough that they have to be avoided does suggest they are incompetent. ... You also kept going on about how one reason for avoiding it could be to avoid broken standard headers. ... if char is not 8 bits you are stuffed in terms of finding an 8 bit type! ...
    (comp.lang.c)