>Number: 2548 >Category: config >Synopsis: apache and php3 both supply an strerror on a system without one >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Fri Jul 3 13:30:01 PDT 1998 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.3.0 >Environment: SunOS 4 system libraries gcc-2.7.2.2 >Description: On SunOS 4, a system without strerror in its provided libraries, both apache-1.3.0 and php-3.0 supply a replacement function named strerror. At link time for httpd, ld complains about a multiple definition and aborts.
I won't venture to say if it is an apache or a php problem. It's rather a question of convention and synchronisation between the two projects. (I will make a similar report to the other php project.) I use php as a static module. (There are worst problems on SunOS in trying to use it as a shared module. I mention this to avoid an "have you tried this", but of course it is not an apache problem.) >How-To-Repeat: >Fix: 3 possibilities: . one or both projects define their replacement function with a prefix that is exclusive to them . apache configuration detects that php3 is used as a static module and provides its own strerr, and so apache does not define NEED_STRERR, even when strerror is not provided by the os . similarly, php does not provide a strerror if it detects that apache will provide one >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. ]
