On Tue, Feb 09, 1999, [EMAIL PROTECTED] wrote:
> I think I got one bug with mod_ssl distrib 2.2.0 and 2.2.2.
> When I run mod_ssl's configure, it ends with "patches applyed succesfully" but
> some errors have created *.rej files. The problem is that I am never get
> notified of those errors.
Are you really sure you don't messed up something locally? I ask because the
patch is applied by etc/apply.sh and this script explicitly checks whether
*.rej files were created:
if [ ".`cd $applydir; find . -name '*.rej' -print`" != . ]; then
failed=1
fi
So, usually when something was rejected, it should complain.
Can you trace down why this check doesn't match for you?
OTOH: When applying mod_ssl to a fresh Apache 1.3.4 source tree, there should
be _NO_ rejected patches. At least not when using the distributed
etc/patch/patch program. Because mod_ssl uses both a well-known patch version
and the patch itself is directly generated out of CVS. So, as long as the
Apache source tree is a fresh one I never have seen the patching process
failing.
So, can you trace down where the problem is for you?
Because I cannot see an obvious error in my sources.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
