openssl/NOTES-DJGPP.md

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

47 lines
2.1 KiB
Markdown
Raw Permalink Normal View History

Notes for the DOS platform with DJGPP
=====================================
2002-06-14 04:42:35 +08:00
2005-01-15 00:25:36 +08:00
OpenSSL has been ported to DJGPP, a Unix look-alike 32-bit run-time
environment for 16-bit DOS, but only with long filename support.
If you wish to compile on native DOS with 8+3 filenames, you will
have to tweak the installation yourself, including renaming files
with illegal or duplicate names.
2002-06-14 04:42:35 +08:00
You should have a full DJGPP environment installed, including the
latest versions of DJGPP, GCC, BINUTILS, BASH, etc. This package
requires that PERL and the PERL module `Text::Template` also be
Revise some renamings of NOTES and README files Some of the notes and readme files have been converted to markdown format recently and renamed during this process. While adding the .md extension was a natural step, switching to mixed cases was not a change to the better, it gives them a ragged appearance: NOTES.ANDROID => NOTES-Android.md NOTES.DJGPP => NOTES-DJGPP.md NOTES.PERL => NOTES-Perl.md NOTES.UNIX => NOTES-Unix.md NOTES.VMS => NOTES-VMS.md NOTES.VALGRIND => NOTES-Valgrind.md NOTES.WIN => NOTES-Windows.txt README.ENGINE => README-Engine.md README.FIPS => README-FIPS.md Moreover, the NOTES-Windows.txt file is the only file which has been converted to markdown but has received a .txt file extension. This doesn't make sense, because the OpenSSL users on Windows will need to read the other markdown documents as well. Since they are developers, we can trust them to be able to associate their favorite editor with the .md extension. In fact, having a comment at the beginning of the file saying that it is in markdown format but we didn't dare to add the correct extension in order not to overwhelm our Windows users can be interpreted either as unintentionally funny or disrespectful ;-) This commit suggests the following more consistent renaming: NOTES.ANDROID => NOTES-ANDROID.md NOTES.DJGPP => NOTES-DJGPP.md NOTES.PERL => NOTES-PERL.md NOTES.UNIX => NOTES-UNIX.md NOTES.VMS => NOTES-VMS.md NOTES.VALGRIND => NOTES-VALGRIND.md NOTES.WIN => NOTES-WINDOWS.md README.ENGINE => README-ENGINES.md README.FIPS => README-FIPS.md (note the plural in README-ENGINES, anticipating a README-PROVIDERS) Reviewed-by: Paul Dale <pauli@openssl.org> (Merged from https://github.com/openssl/openssl/pull/14042)
2021-02-03 01:16:19 +08:00
installed (see [NOTES-PERL.md](NOTES-PERL.md)).
2002-06-14 04:42:35 +08:00
2005-01-15 00:25:36 +08:00
All of these can be obtained from the usual DJGPP mirror sites or
directly at <http://www.delorie.com/pub/djgpp>. For help on which
2005-01-15 00:25:36 +08:00
files to download, see the DJGPP "ZIP PICKER" page at
<http://www.delorie.com/djgpp/zip-picker.html>. You also need to have
2005-01-15 00:25:36 +08:00
the WATT-32 networking package installed before you try to compile
OpenSSL. This can be obtained from <http://www.watt-32.net/>.
2002-12-04 17:54:10 +08:00
The Makefile assumes that the WATT-32 code is in the directory
specified by the environment variable WATT_ROOT. If you have watt-32
in directory `watt32` under your main DJGPP directory, specify
`WATT_ROOT="/dev/env/DJDIR/watt32"`.
2002-06-14 04:42:35 +08:00
2005-01-15 00:25:36 +08:00
To compile OpenSSL, start your BASH shell, then configure for DJGPP by
running `./Configure` with appropriate arguments:
2002-06-14 04:42:35 +08:00
./Configure no-threads --prefix=/dev/env/DJDIR DJGPP
And finally fire up `make`. You may run out of DPMI selectors when
2005-01-15 00:25:36 +08:00
running in a DOS box under Windows. If so, just close the BASH
shell, go back to Windows, and restart BASH. Then run `make` again.
2005-01-10 04:14:04 +08:00
RUN-TIME CAVEAT LECTOR
--------------
Quoting FAQ:
"Cryptographic software needs a source of unpredictable data to work
correctly. Many open source operating systems provide a "randomness
device" (`/dev/urandom` or `/dev/random`) that serves this purpose."
2005-01-10 04:14:04 +08:00
As of version 0.9.7f DJGPP port checks upon `/dev/urandom$` for a 3rd
party "randomness" DOS driver. One such driver, `NOISE.SYS`, can be
obtained from <http://www.rahul.net/dkaufman/index.html>.