os-bsdi/4065: BSDI by default installs a stripped binary, perl can't use dynaload - solution follows

[Doug Silver <ds...@ece.ucsd.edu>]

>Number:         4065
>Category:       os-bsdi
>Synopsis:       BSDI by default installs a stripped binary, perl can't use dynaload - solution follows
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Mon Mar 15 18:10:00 PST 1999
>Last-Modified:
>Originator:     dsilver@ece.ucsd.edu
>Organization:
apache
>Release:        1.3.4
>Environment:
BSD/OS 3.1 BSDI BSD/OS 3.1 Kernel #1: Thu Sep 24 16:43:14 PDT 1998 :/usr/src/sys/compile/  i386
>Description:
BSDI by default wants to install a stripped executable, but if this
happens, then Apache will choke when it tries to dynaload a module.
I found this in DejaNews:
After "make", install with:

        # STRIPPROG=touch make install

and get a nice dynamically linked httpd, *not stripped*. Stripping it
prevents dynamic loading under BSDI 3 -- read dlopen(3).
>How-To-Repeat:

>Fix:
After "make", install with:

        # STRIPPROG=touch make install

** Please put in the BSD Install notes if you can't do it automatically :)

Thanks!
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> 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!         ]