config/6851: libsafe supresses errors during config, can break configuration. can be worked around.

[jose nazario <jo...@cwru.edu>]

>Number:         6851
>Category:       config
>Synopsis:       libsafe supresses errors during config, can break configuration. can be worked around.
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Wed Nov 15 08:50:00 PST 2000
>Closed-Date:
>Last-Modified:
>Originator:     jose@cwru.edu
>Release:        1.3.14
>Organization:
apache
>Environment:
Linux (RedHat 6.2 workstation install) x86, using Apache 1.3.14 sources from the apache foundation.

uname -a reports: Linux test 2.2.14-5.0 #1 Tue Mar 7 21:07:39 EST 2000 i686 unknown

egcs: egcs-1.1.2-30
>Description:
while installing mod_ssl 2.7.1 to the apache 1.3.14 source tree, i was not getting a comepleted configuration. no src/ Makefiles were built. this was with libsafe-1.3-4 installed (from RPM, obtained from  http://www.bell-labs.com/org/11356/libsafe.html). the problem was i had installed OpenSSL 0.9.6 from RPMs, which places the libraries in /usr/lib, headers in /usr/include and apps in /usr/bin, but the default (and what mod_ssl expects) is in /usr/local/ssl. as such, it could not find my ssl libraries and headers, so it could not comeplete installation.

unsetting the LD_PRELOAD option, which libsafe uses, caused these error messages to be generated, revealing the problem. i am unable to acertain why libsafe supressed the error output. 
>How-To-Repeat:
install libsafe from RPM, set LD_PRELOAD (LD_PRELOAD=/lib/libsafe.so.1; export LD_PRELOAD), and now attempt to apply mod_ssl to the apache sources with the wrong OpenSSL installation location. no errors should be generated, and no Makefiles in src should be generated, as well.
>Fix:
when configuring apache, unset LD_PRELOAD. no permanent workaround has been discovered by me.
>Release-Note:
>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 make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database 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!     ]