Hi there,
I would like to report this problem which I stumbled on with both
0.9.8mbeta1 and 1.0.0beta5 (it is probably present in older versions
too).
Usually, when I build a package from source, I run `make -n install' to
see where things will eventually go.
However, to my great surprise, I found that `make -n install' DID
ACTUALLY INSTALL everything!
I was thinking about a possible bug in make, so sent a bug report to
make people: it turned out that the problem is originated by openssl
Makefiles.
The relevant GNU make manual fragment is:
The `-n', `-t', and `-q' options do not affect command lines
that
begin with `+' characters or contain the strings `$(MAKE)' or
`${MAKE}'. Note that only the line containing the `+' character
or the strings `$(MAKE)' or `${MAKE}' is run regardless of these
options.
Basically, if a rule contains `$(MAKE)' or `${MAKE}', then -n
is switched off on the corresponding line. In the case of openssl, this
causes `make -n install' to actually install everything, as I said.
You can read the thread on the subject here:
http://lists.gnu.org/archive/html/bug-make/2010-01/msg00014.html
My workaround is to " sed -e's|\$(MAKE)|make|g' " on every Makefile,
but, of course, I realize that this is at least inelegant!
I do not know whether a real fix for this is easy or not: I just thought I
should have brought this to your attention. I think one should be able
to safely say `make -n install'...
Thanks a lot for making openssl available and for any feedback on this issue
ciao
gabriele
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager majord...@openssl.org
