>Number:         2796
>Category:       os-solaris
>Synopsis:       ap_config.h misses STDIN_FILENO STDOUT_FILENO and STDERR_FILENO
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Thu Aug  6 02:00:01 PDT 1998
>Last-Modified:
>Originator:     [EMAIL PROTECTED]
>Organization:
apache
>Release:        1.3.1
>Environment:
gristle $ uname -a
SunOS gristle 5.6 Generic sun4m sparc SUNW,SPARCstation-5
gristle $ cc -V
cc: WorkShop Compilers 4.2 30 Oct 1996 C 4.2
>Description:
Ok. make dumps out in alloc.c because STD*_FILENO are not defined. I can't
believe no-one else has had this problem, so either I'm a complete incompetent
or everyone else in the world uses gcc.
>How-To-Repeat:
Um. Find a Solaris 2.6 box with the workshop compilers?
>Fix:
OK. Here's a patch. (edited by hand afterwards so I hope it isn't screwed :-)
I've put a bit in to check for the SunPro compiler (I don't have room for gcc
on my machine so I can't test that - but I know other Solaris users who use
gcc).

gristle $ diff -c src/include/ap_config.h src/include/ap_config.h.new >> 
solaris.sunpro.patch
1gristle $ more solaris.sunpro.patch 
*** src/include/ap_config.h     Sat Jul 18 16:30:43 1998
--- src/include/ap_config.h.new Thu Aug  6 09:18:49 1998
***************
*** 164,169 ****
--- 164,175 ----
  #define HAVE_SYSLOG 1
  #define SYS_SIGLIST _sys_siglist
  
+ #ifdef __SUNPRO_C
+ #define STDIN_FILENO  0
+ #define STDOUT_FILENO 1
+ #define STDERR_FILENO 2
+ #endif
+ 
  #elif defined(IRIX)
  #undef HAVE_GMTOFF
  /* IRIX has killpg, but it's only in _BSD_COMPAT, so don't use it in case
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <[EMAIL PROTECTED]> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.                                      ]
[Reply only with text; DO NOT SEND ATTACHMENTS!         ]



Reply via email to