In message <[EMAIL PROTECTED]> on Thu, 7 Jul 2005 11:01:11 +0200, Corinna 
Vinschen <[EMAIL PROTECTED]> said:

vinschen> The problem only happens on filesystems which are not
vinschen> case-sensitive but only case-preserving, like filesystems on
vinschen> Windows or MacOS.
vinschen> 
vinschen> What happens is that make(1) tries to find if the rule is up
vinschen> to date.  While doing this, make calls stat("install"),
vinschen> which returns with success on case-preserving filesystems!

I've applied a fix which looks a little different from yours:

Index: crypto/des/Makefile
===================================================================
RCS file: /e/openssl/cvs/openssl/crypto/des/Makefile,v
retrieving revision 1.5
diff -u -r1.5 Makefile
--- crypto/des/Makefile 16 May 2005 16:55:22 -0000      1.5
+++ crypto/des/Makefile 8 Jul 2005 10:10:55 -0000
@@ -88,7 +88,10 @@
        @$(PERL) $(TOP)/util/mklink.pl ../../test $(TEST)
        @$(PERL) $(TOP)/util/mklink.pl ../../apps $(APPS)
 
-install:
+# We need to use force because 'install' matches 'INSTALL' on case
+# insensitive systems
+FRC.install:
+install: FRC.install
        @[ -n "$(INSTALLTOP)" ] # should be set by top Makefile...
        @headerlist="$(EXHEADER)"; for i in $$headerlist ; \
        do  \


(did the same thing in the crypto/bf directory)

Cheers,
Richard

-----
Please consider sponsoring my work on free software.
See http://www.free.lp.se/sponsoring.html for details.

-- 
Richard Levitte                         [EMAIL PROTECTED]
                                        http://richard.levitte.org/

"When I became a man I put away childish things, including
 the fear of childishness and the desire to be very grown up."
                                                -- C.S. Lewis
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [email protected]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to