Skip to content

Commit

Permalink
Clarify how one should behave when make fails. The fault is not
Browse files Browse the repository at this point in the history
necessarely ours.
  • Loading branch information
levitte committed Sep 8, 2000
1 parent eec79f9 commit a652ffc
Showing 1 changed file with 13 additions and 7 deletions.
20 changes: 13 additions & 7 deletions INSTALL
Original file line number Diff line number Diff line change
Expand Up @@ -124,9 +124,12 @@
OpenSSL binary ("openssl"). The libraries will be built in the top-level
directory, and the binary will be in the "apps" directory.

If "make" fails, please report the problem to <[email protected]>
(note that your message will be forwarded to a public mailing list).
Include the output of "make report" in your message.
If "make" fails, look at the output. There may be reasons for
the failure that isn't a problem in OpenSSL itself (like missing
standard headers). If it is a problem with OpenSSL itself, please
report the problem to <[email protected]> (note that your
message will be forwarded to a public mailing list). Include the
output of "make report" in your message.

[If you encounter assembler error messages, try the "no-asm"
configuration option as an immediate fix.]
Expand All @@ -138,10 +141,13 @@

$ make test

If a test fails, try removing any compiler optimization flags from
the CFLAGS line in Makefile.ssl and run "make clean; make". Please
send a bug report to <[email protected]>, including the
output of "make report".
If a test fails, look at the output. There may be reasons for
the failure that isn't a problem in OpenSSL itself (like a missing
or malfunctioning bc). If it is a problem with OpenSSL itself,
try removing any compiler optimization flags from the CFLAGS line
in Makefile.ssl and run "make clean; make". Please send a bug
report to <[email protected]>, including the output of
"make report".

4. If everything tests ok, install OpenSSL with

Expand Down

0 comments on commit a652ffc

Please sign in to comment.